Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 40984632A2E for ; Tue, 1 Dec 2009 00:04:39 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 37793-03 for ; Tue, 1 Dec 2009 04:04:32 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 04BF26327AB for ; Tue, 1 Dec 2009 00:04:31 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id nB144UZW019404; Mon, 30 Nov 2009 23:04:30 -0500 (EST) To: Bryce Nesbitt cc: pgsql-sql@postgresql.org Subject: Re: pg_restore followed by immediate VACUUM ANALYZE In-reply-to: <4B1494A6.8070300@obviously.com> References: <4B1491A3.6080602@obviously.com> <19189.1259639712@sss.pgh.pa.us> <4B1494A6.8070300@obviously.com> Comments: In-reply-to Bryce Nesbitt message dated "Mon, 30 Nov 2009 19:59:34 -0800" Date: Mon, 30 Nov 2009 23:04:29 -0500 Message-ID: <19403.1259640269@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200912/1 X-Sequence-Number: 33439 Bryce Nesbitt 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.) > Hmm.  It seems like pg_restore would already know 90% of what it needs > to in this case.
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