On 10/29/2015 03:51 PM, Tom Lane wrote: > We don't need hasty patches. What we need is a re-think of the division > of labor between pg_dump and pg_dumpall. Up to now, pg_dump has only been > charged with dumping/restoring the data "inside" an individual database, > not with handling any database-level properties. Those are the > responsibility of pg_dumpall. >
Hello A wiki page with some proposals to improve pg_dump can be found here: https://wiki.postgresql.org/wiki/Pg_dump_improvements It was created sometime ago after a discussion on pgsql-hackers. Refs on the wikipage. regards -- Rafael Martinez Guerrero Center for Information Technology University of Oslo, Norway PGP Public Key: http://folk.uio.no/rafael/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
