Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 63FF864FFC0 for ; Mon, 21 Jul 2008 12:22:57 -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 03222-10 for ; Mon, 21 Jul 2008 12:22:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from alexis.jtlnet.com (alexis.jtlnet.com [69.36.9.81]) by postgresql.org (Postfix) with ESMTP id 424FD64FCD8 for ; Mon, 21 Jul 2008 12:22:53 -0300 (ADT) Received: from [192.168.10.103] (cpe-075-177-154-079.nc.res.rr.com [::ffff:75.177.154.79]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by alexis.jtlnet.com with esmtp; Mon, 21 Jul 2008 11:14:00 -0400 id 00087DC1.4884A7B9.00006147 Message-ID: <4884A90C.1030003@dunslane.net> Date: Mon, 21 Jul 2008 11:19:40 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text SeaMonkey/1.0.9 MIME-Version: 1.0 To: Tom Lane CC: Simon Riggs , Stephen Frost , daveg , pgsql-patches@postgresql.org Subject: Re: pg_dump additional options for performance References: <20080720030749.GA18846@tamriel.snowman.net> <1216529229.19656.835.camel@ebony.2ndQuadrant> <1216535862.19656.845.camel@ebony.2ndQuadrant> <20080720214335.GB18846@tamriel.snowman.net> <1216591180.19656.848.camel@ebony.2ndQuadrant> <20080721011829.GC18846@tamriel.snowman.net> <20080721014942.GC30869@sonic.net> <20080721015850.GD18846@tamriel.snowman.net> <18415.1216611275@sss.pgh.pa.us> <1216621040.19656.867.camel@ebony.2ndQuadrant> <203.1216622870@sss.pgh.pa.us> In-Reply-To: <203.1216622870@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 200807/207 X-Sequence-Number: 6901 Tom Lane wrote: > Simon Riggs writes: > >> I also suggested having three options >> --want-pre-schema >> --want-data >> --want-post-schema >> so we could ask for any or all parts in the one dump. --data-only and >> --schema-only are negative options so don't allow this. >> (I don't like those names either, just thinking about capabilities) >> > > Maybe invert the logic? > > --omit-pre-data > --omit-data > --omit-post-data > > Not wedded to these either, just tossing out an idea... > > > Please, no. Negative logic seems likely to cause endless confusion. I'd even be happier with --schema-part-1 and --schema-part-2 if we can't find some more expressive way of designating them. cheers andrew