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

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: BUG #10315: Transactions seem to be releasing locks early?
Дата
Msg-id CAM-w4HNHh7qj=45cq=b2iH4xb+mD5HcvzmoirZ2AW3o8X4Y0=g@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #10315: Transactions seem to be releasing locks early?  (tim.channell@gmail.com)
Ответы Re: BUG #10315: Transactions seem to be releasing locks early?
Список pgsql-bugs
Дерево обсуждения 
On Tue, May 13, 2014 at 9:51 PM,  <tim.channell@gmail.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: David G Johnston
Дата:
Сообщение: Re: BUG #10315: Transactions seem to be releasing locks early?
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: BUG #10315: Transactions seem to be releasing locks early?