Re: pg_dump/pg_dumpall do not correctly dump search_path - Mailing list pgsql-general

From Oscar Tuscon
Subject Re: pg_dump/pg_dumpall do not correctly dump search_path
Date
Msg-id 20040911193658.B8B50725D@sitemail.everyone.net
Whole thread Raw
In response to pg_dump/pg_dumpall do not correctly dump search_path  ("Ben Trewern" <ben_trewern@hotmail.com>)
List pgsql-general
We have experienced this same problem in 7.4.2.

Oscar

>> Would someone answer this report?.  Looks strange to me.

Ben Trewern wrote:

>> All,
>>
>> There seems to be a bug in pg_dumpall:
>>
>> For one of my dbs I've done:
>>
>> ALTER DATABASE dbname SET search_path = mw, public;
>>
>> If I do a pg_dumpall I get a line like:
>>
>> ALTER DATABASE dbname SET search_path TO 'mw, public';
>>
>> note the 's.  It's also in a place in the dump before the mw schema is
>> created.  It's not a big problem but it makes dumps less automatic.
>>
>> BTW If I do a pg_dump dbname I get a dump which does not reference the
>> search_path change.  I'm not sure if this is by design or it is just
>> missing.
>>
>> I'm using PostgreSQL 7.4.5 on linux
>>
>> Thanks for any help.
>>
>> Ben
>>
>>

_____________________________________________________________
The BMW E30 community on the web---> http://www.bmwe30.net

pgsql-general by date:

Previous
From: Thomas F.O'Connell
Date:
Subject: Re: Another Security Question: User-based Roles vs. Application Business Rules
Next
From: Björn Lundin
Date:
Subject: Re: Storing birthday data