On Tue, Jun 30, 2015 at 3:43 AM, Jeff Janes wrote:
> 2015-06-29 15:18 GMT-07:00 Bráulio Bhavamitra :
>>
>> Hello all,
>>
>> After reading
>> http://stackoverflow.com/questions/9407442/optimise-postgresql-for-fast-testing
>> I've tried to use commit_delay to make commits really slow on a test
>> en
2015-06-29 15:18 GMT-07:00 Bráulio Bhavamitra :
> Hello all,
>
> After reading
> http://stackoverflow.com/questions/9407442/optimise-postgresql-for-fast-testing
> I've tried to use commit_delay to make commits really slow on a test
> environment. Unfortunetely, the maximum value is 100ms (100_000
On Mon, Jun 29, 2015 at 7:43 PM, Tom Lane wrote:
> =?UTF-8?Q?Br=C3=A1ulio_Bhavamitra?= writes:
>> Besides increasing it, it would be great to have these two options
>> (fsync and commit_delay) per database, that is, valid only for
>> databases configured with them. That would greatly speed up tes
=?UTF-8?Q?Br=C3=A1ulio_Bhavamitra?= writes:
> Besides increasing it, it would be great to have these two options
> (fsync and commit_delay) per database, that is, valid only for
> databases configured with them. That would greatly speed up test
> running and still make the cluster available for ot
Hello all,
After reading
http://stackoverflow.com/questions/9407442/optimise-postgresql-for-fast-testing
I've tried to use commit_delay to make commits really slow on a test
environment. Unfortunetely, the maximum value is 100ms (100_000
microseconds).
Besides increasing it, it would be great to
