From: Bryce Nesbitt <bryce2@obviously.com>
To: pgsql-sql@postgresql.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> (raw)
In-Reply-To: <19189.1259639712@sss.pgh.pa.us>
References: <4B1491A3.6080602@obviously.com>
<19189.1259639712@sss.pgh.pa.us>
<!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.1259639712@sss.pgh.pa.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>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bryce2@obviously.com
Subject: Re: pg_restore followed by immediate VACUUM ANALYZE
In-Reply-To: <4B1494A6.8070300@obviously.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox