Re: postgresql transactons not fully isolated

From: Chapman Flack <chap(at)anastigmatix(dot)net>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postgresql transactons not fully isolated
Date: 2017-06-20 19:22:45
Message-ID: 30f0e35d-c91c-ecfa-edc5-9f5c2f8a14ff@anastigmatix.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/20/2017 03:08 PM, Chapman Flack wrote:

> For me (in PG 9.5 at $work), at the instant of the commit in T1,
> T2 says:
> ERROR: could not serialize access due to concurrent update

I get that result in 'serializable' and in 'repeatable read'.

I get the reported result (DELETE 0 and a table containing 2 and 3)
in both 'read committed' and 'read uncommitted'.

-Chap

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2017-06-20 19:34:13 Re: postgresql transactons not fully isolated
Previous Message Tom Lane 2017-06-20 19:18:53 Re: Something is rotten in publication drop