Re: pg_dump bug?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: ohp(at)pyrenet(dot)fr
Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump bug?
Date: 2003-09-01 16:36:58
Message-ID: 200309011636.h81Gawv14806@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ohp(at)pyrenet(dot)fr wrote:
> On Sun, 31 Aug 2003, Bruce Momjian wrote:
>
> > Date: Sun, 31 Aug 2003 21:51:02 -0400 (EDT)
> > From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
> > To: ohp(at)pyrenet(dot)fr
> > Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
> > Subject: Re: [HACKERS] pg_dump bug?
> >
> > ohp(at)pyrenet(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-09-01 16:43:49 Re: Preliminary notes about hash index concurrency (long)
Previous Message Bruce Momjian 2003-09-01 16:35:43 Re: Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...)