Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id CD7A4650183 for ; Sat, 2 Aug 2008 12:24:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 32699-01 for ; Sat, 2 Aug 2008 12:24:23 -0300 (ADT) 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 postgresql.org (Postfix) with ESMTP id 119D964FCE3 for ; Sat, 2 Aug 2008 12:24:22 -0300 (ADT) 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 m72FO1nA003678; Sat, 2 Aug 2008 11:24:01 -0400 (EDT) To: chris cc: pgsql-patches@postgresql.org Subject: Re: pg_dump additional options for performance In-reply-to: <87ej58obpl.fsf@dba2.int.libertyrms.com> References: <20080721115602.GG18846@tamriel.snowman.net> <1216831237.3894.676.camel@ebony.2ndQuadrant> <1216832987.3894.678.camel@ebony.2ndQuadrant> <20080724032047.GI18846@tamriel.snowman.net> <1216885031.3894.739.camel@ebony.2ndQuadrant> <21687.1216886041@sss.pgh.pa.us> <1216889809.3894.747.camel@ebony.2ndQuadrant> <2818.1217027784@sss.pgh.pa.us> <1217063104.3894.1100.camel@ebony.2ndQuadrant> <23540.1217089204@sss.pgh.pa.us> <1217091402.3894.1185.camel@ebony.2ndQuadrant> <24456.1217094974@sss.pgh.pa.us> <87ej58obpl.fsf@dba2.int.libertyrms.com> Comments: In-reply-to chris message dated "Fri, 01 Aug 2008 14:02:30 -0400" Date: Sat, 02 Aug 2008 11:24:01 -0400 Message-ID: <3677.1217690641@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/8 X-Sequence-Number: 6984 chris writes: > Do we need to wait until a fully-parallelizing pg_restore is > implemented before adding this functionality to pg_dump? They're independent problems ... and I would venture that parallel dump is harder. > Further, it's actually not obvious that we *necessarily* care about > parallelizing loading data. The thing that happens every day is > backups. Maybe so, but I would say that routine backups shouldn't be designed to eat 100% of your disk bandwidth anyway --- they'd be more like background tasks. regards, tom lane