Re: Malfunction in dropping database with pgAdmin - Mailing list pgsql-bugs

From Robert Haas
Subject Re: Malfunction in dropping database with pgAdmin
Date
Msg-id 603c8f070908132029y32dea564ldcc4546b81fe57fa@mail.gmail.com
Whole thread Raw
In response to Malfunction in dropping database with pgAdmin  (Sergei Abramov <auspex@rambler.ru>)
Responses Re: Malfunction in dropping database with pgAdmin  (Dave Page <dpage@pgadmin.org>)
List pgsql-bugs
On Tue, Aug 11, 2009 at 2:40 AM, Sergei Abramov<auspex@rambler.ru> wrote:
> Platform: Windows XP, 5.1 (Build 2600).Language: Russain.
> Distribution used: Binary.
> pgAdmin version: 1.10.0.
> PostgreSQL version: 8.4.0-1.
>
> Bug description: When I use pgAdmin's menu command 'Delete/drop' to drop
> database, especially just created, PostgreSQL server reports:
> WARNING: could not remove file or directory "base/16435": Directory not
> empty
> WARNING: some useless files may be left behind in old database directory
> "base/16435".
>
> However, specified directory appears empty and I have to delete it manually.
> Database cluster is situated on local NTFS-drive (or local FAT-drive, just
> for the experiment).
> Note, that using dropdb.exe does not cause such a problem.
> I've already reported this to pgAdmin's support team, they replied it is
> PostgreSQL server that operates wrong...

Do you have a link to the email message from the pgadmin folks?  I'd
be curious what is causing this.

...Robert

pgsql-bugs by date:

Previous
From: "Jim Michaels"
Date:
Subject: BUG #4985: LIMIT documentation is insufficient
Next
From: Robert Haas
Date:
Subject: Re: BUG #4976: pgadmin - reconnect to drop database