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

From Kevin Grittner
Subject Re: BUG #11732: Non-serializable outcomes under serializable isolation
Date
Msg-id 1413916094.99119.YahooMailNeo@web122304.mail.ne1.yahoo.com
Whole thread Raw
In response to Re: BUG #11732: Non-serializable outcomes under serializable isolation  (Peter Bailis <pbailis@cs.berkeley.edu>)
Responses Re: BUG #11732: Non-serializable outcomes under serializable isolation  (Peter Bailis <pbailis@cs.berkeley.edu>)
List pgsql-bugs
Peter Bailis <pbailis@cs.berkeley.edu> wrote:

> 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.
Thanks for checking!

Looking into it....

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Peter Bailis
Date:
Subject: Re: BUG #11732: Non-serializable outcomes under serializable isolation
Next
From: 4OtherBusiness@comcast.net
Date:
Subject: BUG #11748: pgAdmin 3 - fatal missing log file at startup