| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Oskari Saarenmaa <os(at)aiven(dot)io> |
| Cc: | 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-06 06:24:13 |
| Message-ID: | CAM3SWZTEKoR2eJR0v_GR4yOeRyxBsOtViM+_ZFOQTZMBeLB5Gg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jul 5, 2016 at 11:05 PM, Oskari Saarenmaa <os(at)aiven(dot)io> wrote:
> ISTM this is caused by toast knowing nothing about speculative insertion:
> when two backends have executed a speculative heap_insert with a conflicting
> key and the latter one tries to abort after receiving specConflict there's
> nothing in tqual.c to say that the toast rows associated with speculative
> insertion should be visible to that operation.
This analysis may be relevant:
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Timur Luchkin | 2016-07-06 07:47:49 | Re: Too slow "Analyze" for the table with data in Thai language |
| Previous Message | Oskari Saarenmaa | 2016-07-06 06:05:59 | Re: BUG #14150: Attempted to delete invisible tuple |