Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id B76DB2E014C for ; Tue, 19 Feb 2008 15:12:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 32892-01-2 for ; Tue, 19 Feb 2008 15:12:20 -0400 (AST) Received: from hunley.homeip.net (hunley.homeip.net [69.12.222.146]) by postgresql.org (Postfix) with ESMTP id 33DD02E00A3 for ; Tue, 19 Feb 2008 15:08:35 -0400 (AST) Received: from douglas.hunley.homeip.net (d60-34-189.col.wideopenwest.com [65.60.189.34]) (authenticated bits=0) by hunley.homeip.net (8.13.1/8.13.1) with ESMTP id m1JJ8VqH023267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 19 Feb 2008 14:08:37 -0500 From: Douglas J Hunley To: Tom Lane Subject: Re: 7 hrs for a pg_restore? Date: Tue, 19 Feb 2008 14:08:23 -0500 User-Agent: KMail/1.9.7 Cc: Richard Huxton , pgsql-performance@postgresql.org References: <200802191303.58840.doug@hunley.homeip.net> <47BB1C51.6010203@archonet.com> <19241.1203445378@sss.pgh.pa.us> In-Reply-To: <19241.1203445378@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802191408.23960.doug@hunley.homeip.net> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (hunley.homeip.net [69.12.222.146]); Tue, 19 Feb 2008 14:08:37 -0500 (EST) X-Virus-Scanned: ClamAV version 0.92.1, clamav-milter version 0.92.1 on hunley.homeip.net X-Virus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL=0.006 X-Spam-Level: X-Archive-Number: 200802/220 X-Sequence-Number: 28762 On Tuesday 19 February 2008 13:22:58 Tom Lane wrote: > Richard Huxton writes: > > Douglas J Hunley wrote: > >> I spent a whopping seven hours restoring a database late Fri nite for a > > > > Oh, and have you tweaked the configuration settings for the restore? > > Lots of work_mem, turn fsync off, that sort of thing. > > maintenance_work_mem, to be more specific. If that's too small it will > definitely cripple restore speed. I'm not sure fsync would make much > difference, but checkpoint_segments would. See > http://www.postgresql.org/docs/8.3/static/populate.html#POPULATE-PG-DUMP from the postgresql.conf i posted: ~ $ grep maint postgresql.conf maintenance_work_mem = 256MB # min 1MB thx for the pointer to the URL. I've made note of the recommendations therein for next time. > > Also: why did you choose -o ... was there a real need to? I can see > that being pretty expensive. > I was under the impression our application made reference to OIDs. I'm now doubting that heavily and am seeking confirmation. -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 http://doug.hunley.homeip.net I've got trouble with the wife again - she came into the bar looking for me and I asked her for her number.