On Mon, Aug 10, 2009 at 7:51 PM, Guillaume
Lelarge wrote:
> Le lundi 10 août 2009 à 15:48:39, Sergei Abramov a écrit :
>> Database dropping INITIATED BY pgAdmin leads to unability for SERVER
>> (not pgAdmin itself, surely!) to purify database folder. Both in Windows
>> XP and Windows 2000, both NTF
Le lundi 10 août 2009 à 15:48:39, Sergei Abramov a écrit :
> Database dropping INITIATED BY pgAdmin leads to unability for SERVER
> (not pgAdmin itself, surely!) to purify database folder. Both in Windows
> XP and Windows 2000, both NTFS- and FAT-filesystems, the latter being
> used just for experi
Le lundi 10 août 2009 à 11:41:40, Sergei Abramov a écrit :
> I am afraid error is connected with pgAdmin because 'dropdb' does not
> have this shortcoming...
The error messages you paste in your previous mail have nothing to with
pgAdmin. They are server messages. pgAdmin don't delete directories
Le lundi 10 août 2009 à 08:24:30, Sergei Abramov a écrit :
> 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 menu command 'Delete/drop' to drop database,
> PostgreSQL ser
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 menu command 'Delete/drop' to drop database,
PostgreSQL server reports:
WARNING: could not remove file or directory "base/16435":
