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

From Michael Paquier
Subject Re: BUG #14150: Attempted to delete invisible tuple
Date
Msg-id CAB7nPqT4BSnyT+jK9Ys=yuHOe_v5KQ6e-yD7mzrsLC7=A2nfQA@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  (Oskari Saarenmaa <os@aiven.io>)
List pgsql-bugs
On Wed, Jun 29, 2016 at 8:40 AM, Peter Geoghegan <pg@heroku.com> wrote:
> On Mon, Jun 27, 2016 at 8:28 PM, Michael Paquier
> <michael.paquier@gmail.com> wrote:
>> Could you post it? I'd be interested in seeing that.
>
> Attached is a reasonably minimal testcase, showing many "attempted to
> delete invisible tuple" errors for me quickly and reliably. The
> shellscript expects to be able to invoke pgbench without any custom
> arguments, and runs the attach custom pgbench script in an infinite
> loop. On my laptop, there is a roughly 90% chance that the script's 5
> second pgbench runs will raise the error at least once.

Thanks! I can see the problem with that. Now let's dig into it...
--
Michael

pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #14150: Attempted to delete invisible tuple
Next
From: alexey.kuntsevich@gmail.com
Date:
Subject: BUG #14218: pg_logical_slot_get_changes causes segmentation fault