| From: | Sergei Abramov <auspex(at)rambler(dot)ru> |
|---|---|
| To: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Malfunction in dropping database with pgAdmin |
| Date: | 2009-08-11 06:40:53 |
| Message-ID: | 128512531.1249972853.57408680.28255@mcgi72.rambler.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2009-08-11 11:14:46 | misleading error message in 8.5, and bad (?) way deferred uniqueness works |
| Previous Message | Tom Lane | 2009-08-11 03:11:33 | Re: BUG #4973: number precision or scale lost when altering table column |