Skip site navigation (1) Skip section navigation (2)

Re: rmtree() failure on Windows

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Reini Urban <rurban(at)x-ray(dot)at>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: rmtree() failure on Windows
Date: 2004-10-27 14:50:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches

Reini Urban wrote:

>>> 300 secs (!) fs timeout is really broken.
>>> Looks more like a locking or network timeout issue.
>>> What error codes does unlink(3) return?
>> success.
> Oops! 5min timeout for success is certainly problematic.

You misunderstood. The 300 secs is not in waiting for unlink() to 
return, it is in waiting for its effects to be seen by rmdir() (i.e. for 
the entry to actually be cleared from the directory). unlink() is 
returning very quickly. If the bgwriter is disabled then the entries are 
cleared very quickly too (i.e. before we even get to rmdir())



In response to


pgsql-hackers by date

Next:From: Oliver ElphickDate: 2004-10-27 14:59:21
Subject: Re: 8.0b4: COMMIT outside of a transaction echoes
Previous:From: Yann MichelDate: 2004-10-27 14:44:12
Subject: Re: plans for bitmap indexes?

pgsql-patches by date

Next:From: Bruce MomjianDate: 2004-10-27 15:16:53
Subject: Re: rmtree() failure on Windows
Previous:From: Reini UrbanDate: 2004-10-27 14:28:03
Subject: Re: rmtree() failure on Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group