Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 6C8C12E004C for ; Tue, 19 Feb 2008 16:56:00 -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 97432-03 for ; Tue, 19 Feb 2008 16:55:53 -0400 (AST) Received: from hunley.homeip.net (hunley.homeip.net [69.12.222.146]) by postgresql.org (Postfix) with ESMTP id 2495A2E0043 for ; Tue, 19 Feb 2008 16:55:56 -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 m1JKtqd6025702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 19 Feb 2008 15:55:58 -0500 From: Douglas J Hunley To: Jeff Subject: Re: 7 hrs for a pg_restore? Date: Tue, 19 Feb 2008 15:55:43 -0500 User-Agent: KMail/1.9.7 Cc: Tom Lane , Richard Huxton , pgsql-performance@postgresql.org References: <200802191303.58840.doug@hunley.homeip.net> <19241.1203445378@sss.pgh.pa.us> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802191555.43340.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 15:55:58 -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.005 tagged_above=0 required=5 tests=AWL=0.005 X-Spam-Level: X-Archive-Number: 200802/230 X-Sequence-Number: 28772 On Tuesday 19 February 2008 15:07:30 Jeff wrote: > On Feb 19, 2008, at 1:22 PM, Tom Lane wrote: > > 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 > > I wonder if it would be worthwhile if pg_restore could emit a warning > if maint_work_mem is "low" (start flamewar on what "low" is). > > And as an addition to that - allow a cmd line arg to have pg_restore > bump it before doing its work? On several occasions I was moving a > largish table and the COPY part went plenty fast, but when it hit > index creation it slowed down to a crawl due to low maint_work_mem.. fwiw, I +1 this now that I have a (minor) understanding of what's going on, I'd love to do something like: pg_restore -WM $large_value -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 http://doug.hunley.homeip.net There are no dead students here. This week.