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

From Sergei Abramov
Subject Malfunction in dropping database with pgAdmin
Date
Msg-id 128512531.1249972853.57408680.28255@mcgi72.rambler.ru
Whole thread Raw
Responses Re: Malfunction in dropping database with pgAdmin  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
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...

pgsql-bugs by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: misleading error message in 8.5, and bad (?) way deferred uniqueness works
Next
From: Tom Lane
Date:
Subject: Re: misleading error message in 8.5, and bad (?) way deferred uniqueness works