From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
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 00:54:28 |
Message-ID: | 14505.1233276868@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-30 01:06:41 | Re: [GENERAL] Encoding problem using pg_dumpall |
Previous Message | Erik Jones | 2009-01-30 00:00:53 | Re: Pet Peeves? |