From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, ˧ <shuai900217(at)126(dot)com>, 'PostgreSQL-development' <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GSOC] questions about idea "rewrite pg_dump as library" |
Date: | 2013-04-10 21:16:19 |
Message-ID: | 5165D6A3.7080103@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04/10/2013 11:02 PM, Alvaro Herrera wrote:
> Peter Eisentraut wrote:
>
>> I think the main uses cases mentioned in connection with this idea are
>> usually in the direction of finer-grained control over what gets dumped
>> and how. But making pg_dump into a library would not necessarily
>> address that.
> There's also the matter of embedding pg_dump into other programs. For
> example, calling the pg_dump executable from inside pgAdmin is a rather
> messy solution to the problem.
>
Natural solution to this seems to move most of pg_dump functionality
into backend as functions, so we have pg_dump_xxx() for everything
we want to dump plus a topological sort function for getting the
objects in right order.
The main things left into pg_dump the library would be support various ways
to format the dump results into text, tar and "dump" files.
--------------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-04-10 21:24:51 | Re: [GSOC] questions about idea "rewrite pg_dump as library" |
Previous Message | Alvaro Herrera | 2013-04-10 21:02:56 | Re: [GSOC] questions about idea "rewrite pg_dump as library" |