From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: TODO item: Allow more complex user/database default GUC settings |
Date: | 2009-09-30 16:13:55 |
Message-ID: | 24553.1254327235@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-09-30 16:16:27 | Re: Unicode UTF-8 table formatting for psql text output |
Previous Message | Robert Haas | 2009-09-30 16:06:45 | Re: Unicode UTF-8 table formatting for psql text output |