| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | 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-06-29 05:13:22 |
| Message-ID: | CAB7nPqT4BSnyT+jK9Ys=yuHOe_v5KQ6e-yD7mzrsLC7=A2nfQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Jun 29, 2016 at 8:40 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Mon, Jun 27, 2016 at 8:28 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | alexey.kuntsevich | 2016-06-29 07:10:22 | BUG #14218: pg_logical_slot_get_changes causes segmentation fault |
| Previous Message | Peter Geoghegan | 2016-06-28 23:40:34 | Re: BUG #14150: Attempted to delete invisible tuple |