Re: Revisiting BUG #3684: After dump/restore, schema PUBLIC always exists

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=20=20
they create databases and expect "public" to exist.

Furthermore I make my dumps with option -C for pg_dump. The CREATE=20=20
DATABASE statement it generates uses template0 as the template.

> 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=20=20
> yourself is the only logical option for us.

If that's really the case then please add a note in the docs stating=20=20
that deleted objects may revive, so it's no surprise for those who face=20=
=20
that for the first time.

-- Pedro Gimeno