Re: Idea for fixing the Windows fsync problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Idea for fixing the Windows fsync problem
Date: 2007-01-17 00:18:14
Message-ID: 2408.1168993094@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Tom Lane wrote:
>> So: maybe the solution is to add a step to the drop sequence, namely
>> revoking any pending fsync request, before unlink.

> Perhaps we could have the bgwrite check the queue *if* it gets the
> ENOENT/EACCESS error and then re-check the queue for drops on that file?

I've committed a tentative patch along these lines to HEAD. Please
test.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Takayuki Tsunakawa 2007-01-17 00:52:53 Re: O_DIRECT support for Windows
Previous Message Neil Conway 2007-01-16 21:41:14 pgsql: Implement width_bucket() for the float8 data type.