Pedro Gimeno wrote:
> Bruce Momjian wrote:
> > The fact is that 'public' is created from template1, so I suppose if
> > you remove it from there then new databases will not have it.
> That could cause installers for packages using PostgreSQL to fail if
> they create databases and expect "public" to exist.
> Furthermore I make my dumps with option -C for pg_dump. The CREATE
> DATABASE statement it generates uses template0 as the template.
I don't think so. I think it uses template1.
> > I think it would be odd for pg_dump to remove something that was in
> > the database before the restore started. I am afraid removing it
> > yourself is the only logical option for us.
> If that's really the case then please add a note in the docs stating
> that deleted objects may revive, so it's no surprise for those who face
> that for the first time.
You are the first person every to have reported surprise to us, so I am
not inclined to add a documentation until I hear it is a more general
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ If your life is a hard drive, Christ can be your backup. +
In response to
pgsql-bugs by date
|Next:||From: Gregory Stark||Date: 2007-11-10 00:13:31|
|Subject: Re: BUG #3737: lower/upper fails to match extended chars in LATIN1|
|Previous:||From: Pedro Gimeno||Date: 2007-11-09 23:44:53|
|Subject: Re: Revisiting BUG #3684: After dump/restore, schema PUBLIC