On Wed, May 14, 2014 at 9:44 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > The reason that that project has gone untouched for upwards of ten years > is that it's not just a large coding project, but involves a lot of > complex API design with uncertain goals. It's not very clear what > features people would want from a "pg_dump library", though one capability > that gets mentioned often is the ability to extract the SQL definition > for a single object.
Personally I'd prefer the creation of definitional SQL be moved out of pg_dump and into the database proper via something like 'pg_sql_definition(oid)' or something like that. There are lot of reasons applications (especially administrative ones like pgadmin and psql but also end user applications in some cases) would want to do that and forcing everything through pg_dump et al is awkward. The less magic in the external applications the better. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
