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

Re: rmtree() failure on Windows

From: "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>,"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 15:22:37
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA40184D202@m0114.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackers
> >>> 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 

because the bgwriter obviously keeps them open, no ?

Andreas

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-10-27 15:23:00
Subject: Re: rmtree() failure on Windows
Previous:From: Bruce MomjianDate: 2004-10-27 15:16:53
Subject: Re: rmtree() failure on Windows

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