| From: | "Pedro Gimeno" <pgsql-001(at)personal(dot)formauri(dot)es> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #3684: After dump/restore, schema PUBLIC always exists |
| Date: | 2007-10-20 09:37:07 |
| Message-ID: | 200710200937.l9K9b7Am038251@wwwmaster.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 3684
Logged by: Pedro Gimeno
Email address: pgsql-001(at)personal(dot)formauri(dot)es
PostgreSQL version: 8.2.4
Operating system: Debian Etch + Backports
Description: After dump/restore, schema PUBLIC always exists
Details:
In default installations (meaning those having unaltered 'template0'
databases), schema PUBLIC will exist after restoring (via psql) a pg_dump in
text mode done with -C option, even if that schema was deleted in the
original database, since it exists by default and there's no command in the
dump that deletes it. I have not tried using pg_restore or binary dumps,
though.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dawid Kuroczko | 2007-10-20 10:09:40 | Re: PostgreSQL 8.2 Bug in casting varchar to int in SELECT ... WHERE IN ( ... ) |
| Previous Message | Heikki Linnakangas | 2007-10-20 08:09:01 | Re: BUG #3682: Incomplete database restore |