From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bryce Nesbitt <bryce2@obviously.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: pg_restore followed by immediate VACUUM ANALYZE
Date: Mon, 30 Nov 2009 23:04:29 -0500
Message-ID: <19403.1259640269@sss.pgh.pa.us> (raw)
In-Reply-To: <4B1494A6.8070300@obviously.com>
References: <4B1491A3.6080602@obviously.com>
<19189.1259639712@sss.pgh.pa.us>
<4B1494A6.8070300@obviously.com>
Bryce Nesbitt <bryce2@obviously.com> writes:
>> 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>
> Hmm. It seems like pg_restore would already know 90% of what it needs
> to in this case.<br>
But of course pg_restore doesn't know what else you might want to do.
> Of course I'm just trying to cut down on the 4+ hour VACUUM ANALYZE.
You could try just ANALYZE without the VACUUM.
regards, tom lane
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: tgl@sss.pgh.pa.us, bryce2@obviously.com
Subject: Re: pg_restore followed by immediate VACUUM ANALYZE
In-Reply-To: <19403.1259640269@sss.pgh.pa.us>
* 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