Alvaro Herrera <alvhe...@commandprompt.com> writes:
> Tom Lane escribió:
>> Hmm ... I would kind of think that --roles-only should suppress this too.
>> Otherwise you're going to be dumping commands that might refer to
>> nonexistent databases.
> Hmm. The problem I have with this idea is that the only way to dump the
> per-database role settings is if you are also dumping the contents of
> all databases. Which seems like a pain to me because the usage I
> usually recommend is to backup global objects with pg_dumpall -g.
Huh? --globals-only would still dump them, no?
> I wonder if pg_dumpall should have a method for dumping database
> creation and settings, excluding contents (leaving that for plain
> pg_dump).
Perhaps. People keep speculating about refactoring the division of
labor between pg_dump and pg_dumpall. I'd advise leaving that for
a separate patch though ...
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
