| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Oskari Saarenmaa <os(at)aiven(dot)io>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Tripp <peter(at)chartio(dot)com>, Virendra Negi <virendra(at)idyllic-software(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14150: Attempted to delete invisible tuple |
| Date: | 2016-07-07 00:22:14 |
| Message-ID: | CAM3SWZQgq42You9B0+QAOd9K_xMvB5y3iWTMWU9QxHam4p3iYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Jul 6, 2016 at 5:16 PM, Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2016-07-07 00:25:22 | Re: SELECT ... FOR UPDATE OF <table> SKIP LOCKED returns can same row when table is filtered on different table than locked |
| Previous Message | Andres Freund | 2016-07-07 00:16:48 | Re: BUG #14150: Attempted to delete invisible tuple |