Re: pg_restore followed by immediate VACUUM ANALYZE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bryce Nesbitt <bryce2(at)obviously(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: pg_restore followed by immediate VACUUM ANALYZE
Date: 2009-12-01 04:04:29
Message-ID: 19403.1259640269@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Bryce Nesbitt <bryce2(at)obviously(dot)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.&nbsp; 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.&nbsp;

You could try just ANALYZE without the VACUUM.

regards, tom lane

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Gerardo Herzig 2009-12-03 18:05:02 create user xxx with md5 string?
Previous Message Bryce Nesbitt 2009-12-01 03:59:34 Re: pg_restore followed by immediate VACUUM ANALYZE