| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | "pbailis(at)cs(dot)berkeley(dot)edu" <pbailis(at)cs(dot)berkeley(dot)edu>, "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 17:55:24 |
| Message-ID: | 1413914124.90570.YahooMailNeo@web122305.mail.ne1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"pbailis(at)cs(dot)berkeley(dot)edu" <pbailis(at)cs(dot)berkeley(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-10-21 17:55:33 | Re: BUG #11734: The "<<=" operator on "inet" values does not return the expected result. |
| Previous Message | Tom Lane | 2014-10-21 17:49:02 | Re: 32 bit libpq fail to connecting when set a very large "connect_timeout" value |