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-16 20:28:13
Message-ID: 24243.1168979293@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:
> 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?

Hmm ... seems a bit ugly, but then again I've not been able to come up
with a nice way of making the backends wait for queue drain either; and
not having to make them wait at all is certainly attractive. I'll look
into doing it like that. Thanks for the idea!

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jhaile 2007-01-16 20:51:06 Re: PostgreSQL win32 fragmentation issue
Previous Message Tom Lane 2007-01-16 20:19:39 Corner-case bug with outer join equality deductions