On 2014-05-14 10:49:05 -0500, Merlin Moncure wrote: > 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.
That'd be a separate feature from pg_dump though. pg_dump needs to be cross-version compatible and the above prevents that... Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
