Re: BUG #11732: Non-serializable outcomes under serializable isolation

From: Peter Bailis <pbailis(at)cs(dot)berkeley(dot)edu>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #11732: Non-serializable outcomes under serializable isolation
Date: 2014-10-21 18:18:28
Message-ID: CALgH=-PnoturT6eLN37=MEyhaFpqrVezyLig4CRK4A_kEgQPBQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2014-10-21 18:28:14 Re: BUG #11732: Non-serializable outcomes under serializable isolation
Previous Message John R Pierce 2014-10-21 18:02:11 Re: 32 bit libpq fail to connecting when set a very large "connect_timeout" value