Re: BUG #10315: Transactions seem to be releasing locks early?

From: Greg Stark <stark(at)mit(dot)edu>
To: tim(dot)channell(at)gmail(dot)com
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #10315: Transactions seem to be releasing locks early?
Date: 2014-05-14 03:21:55
Message-ID: CAM-w4HNHh7qj=45cq=b2iH4xb+mD5HcvzmoirZ2AW3o8X4Y0=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, May 13, 2014 at 9:51 PM, <tim(dot)channell(at)gmail(dot)com> wrote:
> 7. Back in the second transaction, our DELETE has executed because the lock
> was released. It would be expected to show "DELETE 1", because the first
> transaction re-inserted the deleted record. But, it shows DELETE 0.

It can't see the second row because it was inserted after the delete
query started.

I think in SERIALIZABLE mode it would be flagged as a serialization
failure but I'm not sure.

--
greg

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2014-05-14 12:06:07 Re: BUG #10315: Transactions seem to be releasing locks early?
Previous Message David G Johnston 2014-05-13 21:36:55 Re: BUG #10315: Transactions seem to be releasing locks early?