X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B317D9FA5C3 for ; Thu, 8 Jun 2006 22:17:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 61118-03 for ; Thu, 8 Jun 2006 22:16:59 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from houston.familyhealth.com.au (iihouston.familyhealth.com.au [203.59.102.239]) by postgresql.org (Postfix) with ESMTP id E931B9FA3CD for ; Thu, 8 Jun 2006 22:16:59 -0300 (ADT) Received: from houston.familyhealth.com.au (localhost [127.0.0.1]) by houston.familyhealth.com.au (Postfix) with ESMTP id 0F73125740; Fri, 9 Jun 2006 09:16:58 +0800 (WST) Received: from [127.0.0.1] (work-48.internal [192.168.0.48]) by houston.familyhealth.com.au (Postfix) with ESMTP id B95082573A; Fri, 9 Jun 2006 09:16:55 +0800 (WST) Message-ID: <4488CC93.5040709@calorieking.com> Date: Fri, 09 Jun 2006 09:19:15 +0800 From: Christopher Kings-Lynne User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: "Jim C. Nasby" , soni de , pgsql-performance@postgresql.org Subject: Re: Regarding pg_dump utility References: <9f2e40a90606072309v4c5b2623k8bda2614cd575835@mail.gmail.com> <20060608151657.GL45331@pervasive.com> <20060608162327.GD17421@surnet.cl> In-Reply-To: <20060608162327.GD17421@surnet.cl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-familyhealth-MailScanner-Information: Please contact the ISP for more information X-familyhealth-MailScanner: Found to be clean X-familyhealth-MailScanner-From: chris.kings-lynne@calorieking.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/105 X-Sequence-Number: 19462 > Personally I think it would be neat. For example the admin-tool guys > would be able to get a dump without invoking an external program. > Second it would really be independent of core releases (other than being > tied to the output format.) pg_dump would be just a simple caller of > such a library, and anyone else would be able to get dumps easily, in > whatever format. What about fully completing our SQL API for dumping? ie. We finish adding pg_get_blahdef() for all objects, add a function that returns the proper ordering of all objects in the database, and then somehow drop out a dump with a single JOIN :D Chris