Re: 9.2 upgrade glitch with search_path - Mailing list pgsql-general

From Scott Ribe
Subject Re: 9.2 upgrade glitch with search_path
Date
Msg-id 86FC2B9F-131A-4F9D-803D-73755346BD8F@elevated-dev.com
Whole thread Raw
In response to Re: 9.2 upgrade glitch with search_path  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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'vealways used pg_dumpall. 

--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice






pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: 9.2 upgrade glitch with search_path
Next
From: Steve Atkins
Date:
Subject: VALUES() evaluation order