| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Postgresql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: 9.2 upgrade glitch with search_path |
| Date: | 2013-01-13 22:18:26 |
| Message-ID: | 86FC2B9F-131A-4F9D-803D-73755346BD8F@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jan 13, 2013, at 2:51 PM, Tom Lane wrote:
> That's a hole in the particular dump methodology you selected:
>
>> pg_dumpall -g -f roles.dump
>> pg_dump -F c -Z 0 -v pedcard > db.dump
>
> pg_dump does not dump/restore database properties, only database
> contents. Properties are the responsibility of pg_dumpall, which
> you bypassed (for databases anyway).
>
> There's been some discussion of refactoring these responsibilities,
> but no consensus.
Ah, this is my first upgrade using that methodology, in order to get concurrent restore functionality. Prior to this I've always used pg_dumpall.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2013-01-13 22:19:25 | VALUES() evaluation order |
| Previous Message | Tom Lane | 2013-01-13 21:51:55 | Re: 9.2 upgrade glitch with search_path |