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 CAM3SWZS0u0LcoYbeUp0TQFcR--p8LdDrMmySqXP7i_pYbnP9=w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14150: Attempted to delete invisible tuple  (Peter Geoghegan <pg@heroku.com>)
Responses Re: BUG #14150: Attempted to delete invisible tuple
List pgsql-bugs
On Wed, Jul 27, 2016 at 6:12 PM, Peter Geoghegan <pg@heroku.com> wrote:
> On Wed, Jul 27, 2016 at 6:04 PM, Andres Freund <andres@anarazel.de> wrote:
>> That it needs a test, or that it's easy to do?
>
> That it's easy to write one.

I'll be more concrete: I don't see what choke point is available to
make control yield after the pre-check determines there is no
conflict, but before index tuple insertion determines that there is in
fact a conflict (to reliably trigger a failed specualtive
insertion/super deletion).

--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #14269: Postgres JDBC driver should be able to connect using protocol version 2 to server versions 9.5+
Next
From: Peter Eisentraut
Date:
Subject: Re: BUG #14170: error message in case LOCALE de_DE.UTF8 is used in combination with CLIENT_ENCODING=LATIN1