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 5FD959FA61D for ; Fri, 9 Jun 2006 11:22:57 -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 41808-07 for ; Fri, 9 Jun 2006 11:22:51 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.198]) by postgresql.org (Postfix) with ESMTP id 2AE049F9316 for ; Fri, 9 Jun 2006 11:22:51 -0300 (ADT) Received: by nz-out-0102.google.com with SMTP id l1so712374nzf for ; Fri, 09 Jun 2006 07:22:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=R1rMipeLPqskOa5xELM2eq+SjuBEJEbrro3FTeJ7krGBwDxEQEWs2u4upHRJ/GgDep6vHDZxpnmtXyfJQ9wpciav3bZka/huXFEx4gsMwqU+pbAe725pv2PXKECFL3y12BtwG2kB/9plmfWFfD4EwPkEdf99CJl3+alFvUH8RZ4= Received: by 10.37.2.14 with SMTP id e14mr4143687nzi; Fri, 09 Jun 2006 07:22:50 -0700 (PDT) Received: by 10.37.14.7 with HTTP; Fri, 9 Jun 2006 07:22:50 -0700 (PDT) Message-ID: <866624ef0606090722n3779b835l316035b2a04b75e1@mail.gmail.com> Date: Fri, 9 Jun 2006 10:22:50 -0400 From: "Paul S" To: pgsql-performance@postgresql.org Subject: Re: Regarding pg_dump utility In-Reply-To: <4488CC93.5040709@calorieking.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10764_6572683.1149862970257" References: <9f2e40a90606072309v4c5b2623k8bda2614cd575835@mail.gmail.com> <20060608151657.GL45331@pervasive.com> <20060608162327.GD17421@surnet.cl> <4488CC93.5040709@calorieking.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/110 X-Sequence-Number: 19467 ------=_Part_10764_6572683.1149862970257 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I think that having an API for backup functionality would definitely be useful. Just my 2 cents... Paul On 6/8/06, Christopher Kings-Lynne wrote: > > > 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 > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > ------=_Part_10764_6572683.1149862970257 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
I think that having an API for backup functionality would definitely be useful. 
 
Just my 2 cents...
 
Paul
 


 
On 6/8/06, Christopher Kings-Lynne <chris.kings-lynne@calorieking.com> wrote:
> 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


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

------=_Part_10764_6572683.1149862970257--