Josh Berkus wrote: > On 07/28/2015 11:58 AM, Robert Haas wrote: > > I'd be strongly in favour of teaching GRANT, SECURITY LABEL, COMMENT > >> ON DATABASE, etc to recognise CURRENT_DATABASE as a keyword. Then > >> dumping them in pg_dump --create, and in pg_dump -Fc . > >> > >> In practice I see zero real use of pg_dumpall without --globals-only, > >> and almost everyone does pg_dump -Fc . I'd like to see that method > >> case actually preserve the whole state of the system and do the right > >> thing sensibly. > >> > >> A pg_restore option to skip database-level settings could be useful, > >> but I think by default they should be restored. > > +++++1 > > Let's get rid of pg_dumpall -g.
Quite the opposite, I think --- let's get rid of pg_dumpall EXCEPT when invoked as pg_dumpall -g. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, 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
