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

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Peter Bailis <pbailis(at)cs(dot)berkeley(dot)edu>
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:28:14
Message-ID: 1413916094.99119.YahooMailNeo@web122304.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Bailis <pbailis(at)cs(dot)berkeley(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 4OtherBusiness 2014-10-22 00:11:33 BUG #11748: pgAdmin 3 - fatal missing log file at startup
Previous Message Peter Bailis 2014-10-21 18:18:28 Re: BUG #11732: Non-serializable outcomes under serializable isolation