From: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Gerhard Wiesinger <lists(at)wiesinger(dot)com>, "Raymond O'Donnell" <rod(at)iol(dot)ie>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Full backup - pg_dumpall sufficient? |
Date: | 2009-01-30 02:34:04 |
Message-ID: | 4982671C.9020801@frostconsultingllc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jeff Frost wrote:
> On Thu, 29 Jan 2009, Tom Lane wrote:
>
>> Jeff Frost <jeff(at)frostconsultingllc(dot)com> writes:
>>> Tom one thing I noticed recently is that pg_dumpall --globals doesn't
>>> seem to pick up when you alter the GUCs at the database level and
>>> neither does pg_dump. How should you dump to grab that per-database
>>> stuff?
>>
>> Regular pg_dumpall will catch that.
>>
>> There's been some previous discussion about redrawing the dividing lines
>> so that this doesn't fall between the cracks when you try to use
>> --globals plus per-database pg_dump, but AFAIR nothing's been done about
>> it yet. It's a bit tricky since it's not entirely clear who's
>> responsible for creating the individual databases when you restore in
>> that scenario.
>
> I guess I could pg_dumpall -s | grep "ALTER DATABASE" to grab that stuff.
>
That seems silly. Is this the best way to find this data:
SELECT name, setting FROM pg_settings where source = 'database' ORDER BY
name;
?
--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 916-647-6411 FAX: 916-405-4032
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-30 02:39:37 | Re: Full backup - pg_dumpall sufficient? |
Previous Message | Adrian Klaver | 2009-01-30 01:53:37 | Re: Pet Peeves? |