tom is talking about the postgresql distributed buildfarm:
Thank you for telling me. This is a great system, isn't it?
----- Original Message -----
From: "Stefan Kaltenbrunner" <[EMAIL PROTECTED]>
To: "Takayuki Tsunakawa" <[EMAIL PROTECTED]>
Cc: "Magnus Hagander" <[EMAIL PROTECTED]>;
<firstname.lastname@example.org>; "Tom Lane" <[EMAIL PROTECTED]>
Sent: Wednesday, January 17, 2007 4:44 PM
Subject: Re: [HACKERS] Idea for fixing the Windows fsync problem
> Takayuki Tsunakawa wrote:
>> From: "Tom Lane" <[EMAIL PROTECTED]>
>>> I wrote:
>>>> I've committed a tentative patch along these lines to HEAD.
>>> 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
>>> hindsight it's quite obvious that if the bgwriter is to take a
>>> 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
>>> 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
>> Is everyone is able to see the test result freely? Sorry, I'll
>> developer's FAQ when I have more time.
> tom is talking about the postgresql distributed buildfarm:
> and right now most of the members are indeed "red" due to the fsync
> related changes.
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?