Re: BUG #11732: Non-serializable outcomes under serializable isolation - Mailing list pgsql-bugs

From Peter Bailis
Subject Re: BUG #11732: Non-serializable outcomes under serializable isolation
Date
Msg-id CALgH=-PnoturT6eLN37=MEyhaFpqrVezyLig4CRK4A_kEgQPBQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #11732: Non-serializable outcomes under serializable isolation  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: BUG #11732: Non-serializable outcomes under serializable isolation  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-bugs
>
> I'm just starting to look at this, but it would help if you could
> try with the same conditions where you are seeing the failure, but
> with max_pred_locks_per_transaction = 1280 (or higher).


I just re-ran the workload with max_pred_locks_per_transaction set (in
postgresql.conf) to each of 1280, 12800, and 128000  and observed the
duplicate behavior under each setting.

pgsql-bugs by date:

Previous
From: John R Pierce
Date:
Subject: Re: 32 bit libpq fail to connecting when set a very large "connect_timeout" value
Next
From: Kevin Grittner
Date:
Subject: Re: BUG #11732: Non-serializable outcomes under serializable isolation