From: | Oscar Tuscon <obtuse(at)bmwe30(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump/pg_dumpall do not correctly dump search_path |
Date: | 2004-09-11 19:36:58 |
Message-ID: | 20040911193658.B8B50725D@sitemail.everyone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Dr. Aharon Friedman | 2004-09-11 21:19:52 | Synchronizing Databases |
Previous Message | Karl O. Pinc | 2004-09-11 19:27:03 | Re: Obtaining the Julian Day from a date |