Re: BUG #14150: Attempted to delete invisible tuple

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Geoghegan <pg(at)heroku(dot)com>
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-06 21:40:45
Message-ID: 20160706214045.ommbu37ui6nufscf@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2016-07-05 23:24:13 -0700, Peter Geoghegan wrote:
> 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:
>
> https://www.postgresql.org/message-id/CACjxUsMBEHexQehM6P7ck+7AdxReH9fP29Z3t6h4eZp_9YveXQ@mail.gmail.com

Not sure what that has to do with the problem?

Andres

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Gierth 2016-07-06 22:43:16 Re: BUG #14231: logical replication wal sender process spins when using error traps in function
Previous Message Andres Freund 2016-07-06 21:40:24 Re: BUG #14150: Attempted to delete invisible tuple