Re: BUG #14150: Attempted to delete invisible tuple - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #14150: Attempted to delete invisible tuple
Date
Msg-id CAM3SWZQgq42You9B0+QAOd9K_xMvB5y3iWTMWU9QxHam4p3iYw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14150: Attempted to delete invisible tuple  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #14150: Attempted to delete invisible tuple
List pgsql-bugs
On Wed, Jul 6, 2016 at 5:16 PM, Andres Freund <andres@anarazel.de> wrote:
>> And so, in simpler words, you believe that any
>> heap_abort_speculative() call to toast_delete() will cause this error
>> to be raised?
>
> Looks that way, yes.

The reason I doubted that it could be that simple was that it took
this long to hear about this bug. It also took me a little while to
produce a test case. I tended to doubt that all toast_delete() calls
from heap_abort_speculative() are broken, since ISTM that they're not
very rare in practice.

I may have been wrong about that, though.

--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #14150: Attempted to delete invisible tuple
Next
From: Thomas Munro
Date:
Subject: Re: SELECT ... FOR UPDATE OF SKIP LOCKED returns can same row when table is filtered on different table than locked