Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: pg_restore followed by immediate VACUUM ANALYZE
- From: Bryce Nesbitt <bryce2(at)obviously(dot)com>
- To: pgsql-sql(at)postgresql(dot)org
- Subject: Re: pg_restore followed by immediate VACUUM ANALYZE
- Date: Mon, 30 Nov 2009 19:59:34 -0800
- Message-id: <4B1494A6.8070300@obviously.com> <text/plain>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Tom Lane wrote:<br>
<blockquote cite="mid:19189(dot)1259639712(at)sss(dot)pgh(dot)pa(dot)us" type="cite">
<blockquote type="cite">
<pre wrap="">Does pg_restore not update the query planner statistics?
</pre>
</blockquote>
<pre wrap=""><!---->
Correct. Autovacuum might fix them eventually, but usually it's
worth forcing the issue once you've completed your data loading.
(This might involve multiple steps, which is why pg_restore
doesn't try to force it for you.)</pre>
</blockquote>
Hmm. It seems like pg_restore would already know 90% of what it needs
to in this case.<br>
Of course I'm just trying to cut down on the 4+ hour VACUUM ANALYZE.
But thanks for<br>
the note, I'll look elsewhere for speed improvements.<br>
</body>
</html>
- References:
- pg_restore followed by immediate VACUUM ANALYZE
- From: Bryce Nesbitt
- Re: pg_restore followed by immediate VACUUM ANALYZE
- From: Tom Lane
- pg_restore followed by immediate VACUUM ANALYZE
- Prev by Date: Re: pg_restore followed by immediate VACUUM ANALYZE
- Previous by thread: Re: pg_restore followed by immediate VACUUM ANALYZE
- Indexes: