Re: Correct behaviour of "DROP DATABASE" - Mailing list pgsql-general

From Ben Leslie
Subject Re: Correct behaviour of "DROP DATABASE"
Date
Msg-id 20010227173206.A9364@sesgroup.net
Whole thread Raw
In response to Re: Correct behaviour of "DROP DATABASE"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Mon, 26 Feb 2001, Tom Lane wrote:

> Ben Leslie <benno@sesgroup.net> writes:
> > I was wondering what the expected behaviour of "DROP DATABASE" was.
>
> > Basically the problem i have is that when I drop a database it seems
> > to drop only some of the associated tables.
>
> That is *real* hard to believe, considering that the entire database
> including system catalogs is physically removed (rm -rf no less) by
> DROP DATABASE.  There is nothing left in which table names could
> appear, mixed-case or otherwise, much less the tables themselves.
>
> What PG version are you running, and exactly what are you doing that
> gives you unexpected results?
>

Sorry, my bad. I managed to screw things up so it looked as though
that is what was happening, but it wasn't.

Apologies for wasting time.

Benno

pgsql-general by date:

Previous
From: brichard@cafod.org.uk (Bruce Richardson)
Date:
Subject: Case sensitivity
Next
From: Richard Huxton
Date:
Subject: Re: Postgresql and ODBC