Re: Testing the async-commit patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Testing the async-commit patch
Date: 2007-08-13 19:17:17
Message-ID: 19539.1187032637@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julius Stroffek 2007-08-13 19:49:56 Proposal: Pluggable Optimizer Interface
Previous Message Tom Lane 2007-08-13 19:15:21 Re: Testing the async-commit patch