I have a database 'testdb' with two schemas: 'public' and edinburgh'.
Public is empty, everything is in 'edinburgh'.

DROP DATABASE testdb;

Database no longer appears in list of databases in cluster. So far, so good.

CREATE DATABASE testdb;

Database appears again. But so does the schema 'edinburgh', all its
tables, views, data, etc.

From reading the documentation, I thought that "DROP DATABASE" also
deleted all the underlying objects. In which case, this is a bug.

BTW, this is my first post of a postgresql bug. It would be useful if
your page
<http://www.postgresql.org/docs/current/static/bug-reporting.html> had a
link to where the "TODO LIST" and "FAQ" files can be found - it's not
obvious unless you already know!

Thanks
Rachel

PS: System is PostgreSQL 7.4.2 on i686-pc-linux-gnu, compiled by GCC gcc
(GCC) 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3-3-7)


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Rachel Willmer <rachel (AT) willmer (DOT) com> writes:
Sounds like you created all that stuff in template1, and so it's being
copied into the new database. Read about template databases:
http://www.postgresql.org/docs/7.4/s...mplatedbs.html

If you decide you want to rebuild template1 without re-initdb'ing,
there's a recipe somewhere on the techdocs site --- it's not quite
a trivial thing to do.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Tom Lane wrote:

Yup, that's it. Thanks!
Rachel

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org