Re: Testing the async-commit patch - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Testing the async-commit patch
Date
Msg-id 19539.1187032637@sss.pgh.pa.us
Whole thread Raw
In response to Re: Testing the async-commit patch  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> "Tom Lane" <tgl@sss.pgh.pa.us> writes:
>> I propose that we actually set synchronous_commit
>> off by default for the next little while --- at least up to 8.3beta1,
>> maybe until we approach the RC point.  That will ensure that every
>> buildfarm machine is exercising the async-commit behavior, as well as
>> every developer who's testing HEAD.
>> 
>> Of course the risk is that we might forget to turn it back on before
>> release :-(

> I'll set a cron job to remind us. What date should I set it for? :)

I thought of a low-tech solution for that: put a note in
src/tools/RELEASE_CHANGES about it.  We invariably look at that file
while preparing releases.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Testing the async-commit patch
Next
From: Julius Stroffek
Date:
Subject: Proposal: Pluggable Optimizer Interface