pg_dump/pg_dumpall do not correctly dump search_path
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
_________________________________________________________________
Stay in touch with absent friends - get MSN Messenger
http://www.msn.co.uk/messenger
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
_________________________________________________________________
Stay in touch with absent friends - get MSN Messenger
http://www.msn.co.uk/messenger---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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
Import Notes
Resolved by subject fallback