BUG #13667: SSI violation...

From: sean(at)chittenden(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #13667: SSI violation...
Date: 2015-10-08 10:00:36
Message-ID: 20151008100036.8427.63845@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 13667
Logged by: Sean Chittenden
Email address: sean(at)chittenden(dot)org
PostgreSQL version: 9.4.4
Operating system: Linux/FreeBSD
Description:

A few weeks back I was pointed in the direction of a bug that appears to be
an SSI violation. The repro case below is written using bash and psql.

In a tight loop, we would expect 50% of these transactions to fail.
Instead, periodically we're seeing both transaction commit successfully.
The concern is that PostgreSQL thinks these transactions are commutable or
the SIREAD lock isn't erected correctly.

https://github.com/gfredericks/pg-serializability-bug

The two concurrent transactions required to tickle this bug are:

BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE;
INSERT INTO things (id) VALUES ('A');
SELECT id FROM things;
COMMIT;

BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE;
INSERT INTO things (id) VALUES ('B');
SELECT id FROM things;
COMMIT;

Cheers. -sc

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message rama2.s 2015-10-08 10:53:34 BUG #13668: Production server Crash
Previous Message Jarl Walker 2015-10-08 02:37:12 Re: BUG #13663: uuid-ossp in multiple schemas same database