Re: rmtree() failure on Windows

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Reini Urban <rurban(at)x-ray(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: rmtree() failure on Windows
Date: 2004-10-27 16:00:35
Message-ID: 20850.1098892835@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> 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())

More specifically, 300 seconds is the most time you'd have to wait for a
checkpoint to occur (with default checkpoint settings) ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Leen Besselink 2004-10-27 16:23:28 pg_autovacuum in 8beta-dev3 small bug
Previous Message Tom Lane 2004-10-27 15:58:09 Re: rmtree() failure on Windows

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-10-27 16:20:47 Re: pgstat cleanup: use palloc and AllocateFile
Previous Message Tom Lane 2004-10-27 15:58:09 Re: rmtree() failure on Windows