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: 417FB5AB.7070602@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-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())

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

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

Browse pgsql-patches by date

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