Re: pg_dumpall (7.3) 'public' schema bug

From: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Karl O(dot) Pinc" <kop(at)meme(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_dumpall (7.3) 'public' schema bug
Date: 2004-11-16 23:05:18
Message-ID: 20041116170518.E3148@mofo.meme.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On 2004.11.16 16:25 Tom Lane wrote:
> "Karl O. Pinc" <kop(at)meme(dot)com> writes:
> > I deleted the 'public' schema from my databases
> > in 7.3, now in 7.4 they are back.
>
> IMHO this is not a bug. It is not pg_dump's charter to remove
> system-created objects...

I can live with this, but I find the implication distasteful --
that there is no way to move a database from one cluster
to another and have an exact copy. Not even when both
clusters are running the same release.

I don't care that much about the behavior, it's easy enough
to delete 'public'. I do think that a note should be
made in the administrator manual regards system upgrades
where pg_dump(all) scripts are given if this is going to be
the behavior.

Thanks for postgresql.

Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew - Supernews 2004-11-16 23:39:40 Re: libplperl.so and libperl.so
Previous Message Tom Lane 2004-11-16 22:56:22 Re: BUG #1321: SSL error: sslv3 alert handshake failure