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 1413914124.90570.YahooMailNeo@web122305.mail.ne1.yahoo.com
Whole thread Raw
In response to BUG #11732: Non-serializable outcomes under serializable isolation  (pbailis@cs.berkeley.edu)
Responses Re: BUG #11732: Non-serializable outcomes under serializable isolation  (Peter Bailis <pbailis@cs.berkeley.edu>)
List pgsql-bugs
"pbailis@cs.berkeley.edu" <pbailis@cs.berkeley.edu> wrote:

> I'm happy to debug further, but I'm sending what I have so far.


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).  It appears
that you are pushing things to the point where it is likely to be
summarizing the predicate locks of multiple transactions; the above
will help to establish whether the bug is in that area of the code
or somewhere else.

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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: 32 bit libpq fail to connecting when set a very large "connect_timeout" value
Next
From: Tom Lane
Date:
Subject: Re: BUG #11734: The "<<=" operator on "inet" values does not return the expected result.