From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Takayuki Tsunakawa <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Idea for fixing the Windows fsync problem |
Date: | 2007-01-17 07:44:57 |
Message-ID: | 45ADD3F9.4090904@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Takayuki Tsunakawa wrote:
> From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | tomas | 2007-01-17 07:49:48 | Re: Autovacuum improvements |
Previous Message | ITAGAKI Takahiro | 2007-01-17 07:43:30 | Re: Dead Space Map for vacuum |