From: Paul S <plabrh1@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Regarding pg_dump utility
Date: Fri, 9 Jun 2006 10:22:50 -0400
Message-ID: <866624ef0606090722n3779b835l316035b2a04b75e1@mail.gmail.com> (raw)
In-Reply-To: <4488CC93.5040709@calorieking.com>
References: <9f2e40a90606072309v4c5b2623k8bda2614cd575835@mail.gmail.com>
<20060608151657.GL45331@pervasive.com>
<20060608162327.GD17421@surnet.cl>
<4488CC93.5040709@calorieking.com>
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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: plabrh1@gmail.com
Subject: Re: Regarding pg_dump utility
In-Reply-To: <866624ef0606090722n3779b835l316035b2a04b75e1@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox