Re: pg_dump bug? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_dump bug?
Date
Msg-id 200309011636.h81Gawv14806@candle.pha.pa.us
Whole thread Raw
In response to Re: pg_dump bug?  (ohp@pyrenet.fr)
List pgsql-hackers
ohp@pyrenet.fr wrote:
> On Sun, 31 Aug 2003, Bruce Momjian wrote:
> 
> > Date: Sun, 31 Aug 2003 21:51:02 -0400 (EDT)
> > From: Bruce Momjian <pgman@candle.pha.pa.us>
> > To: ohp@pyrenet.fr
> > Cc: pgsql-hackers list <pgsql-hackers@postgresql.org>
> > Subject: Re: [HACKERS] pg_dump bug?
> >
> > ohp@pyrenet.fr wrote:
> > > Hi all,
> > >
> > > This is on 7.3.4
> > > I had altered a user like this:
> > > alter user set search_path = shema1,public
> > >
> > > Then I had to pgdumpall, re-initdb and restore every thing.
> > >
> > > The alter user did'nt get through. and broke my app.
> >
> > Yes, it seems pg_dump doesn't dump per-database alter information, only
> > pg_dumpall does.  That information is considered global to the cluster,
> > rather than per-database.
> Err, I had done a pg_dumpall..
> Does alter database set serach_pat = blah works on 7.3.4?

Oh 7.3.4.  (I see that above now.) Maybe it was a bug.  It works fine in
7.4.

--  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,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...)
Next
From: Bruce Momjian
Date:
Subject: Re: Preliminary notes about hash index concurrency (long)