Re: Correct behaviour of "DROP DATABASE"

From: Ben Leslie <benno(at)sesgroup(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Correct behaviour of "DROP DATABASE"
Date: 2001-02-27 06:32:06
Message-ID: 20010227173206.A9364@sesgroup.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 26 Feb 2001, Tom Lane wrote:

> Ben Leslie <benno(at)sesgroup(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2001-02-27 07:57:46 Re: Postgresql and ODBC
Previous Message Bruce Richardson 2001-02-27 05:47:12 Case sensitivity