Re: Idea for fixing the Windows fsync problem

Hello, Stefan-san
tom is talking about the postgresql distributed buildfarm:
>
> http://buildfarm.postgresql.org/cgi-bin/show_status.pl

Thank you for telling me.  This is a great system, isn't it?

----- Original Message ----- 
From: "Stefan Kaltenbrunner" <stefan@kaltenbrunner.cc>
To: "Takayuki Tsunakawa" <tsunakawa.takay@jp.fujitsu.com>
Cc: "Magnus Hagander" <magnus@hagander.net>;
<pgsql-hackers@postgresql.org>; "Tom Lane" <tgl@sss.pgh.pa.us>
Sent: Wednesday, January 17, 2007 4:44 PM
Subject: Re: [HACKERS] Idea for fixing the Windows fsync problem


> Takayuki Tsunakawa wrote:
>> From: "Tom Lane" <tgl@sss.pgh.pa.us>
>>> I wrote:
>>>> I've committed a tentative patch along these lines to HEAD.
Please
>>>> test.
>>> So I come home from dinner out, and find the buildfarm all red :-(
>>>
>>> I'm not sure why I didn't see this failure in my own testing, but
in
>>> hindsight it's quite obvious that if the bgwriter is to take a
hard
>>> line about fsync failures, it's got to be told about DROP DATABASE
>>> not only DROP TABLE --- that is, there has to be a signaling
message
>>> for "revoke fsync requests across whole database".
>>>
>>
>> Excuse me if I misunderstand English and say something strange.
>> I thought "buildfarm is red" meant the failure of regression test.
>> What kind of errors did you get in what operation (e.g. DROP
INDEX)?
>> Is everyone is able to see the test result freely?  Sorry, I'll
read
>> developer's FAQ when I have more time.
>
> tom is talking about the postgresql distributed buildfarm:
>
> http://buildfarm.postgresql.org/cgi-bin/show_status.pl
>
> and right now most of the members are indeed "red" due to the fsync
> related changes.
>
>
> Stefan
>