| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(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-28 23:40:34 |
| Message-ID: | CAM3SWZRE3eYZyrJz78mTNB5nG0sB47=z+S-T8HSq3h-_2PzcYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
If this doesn't work for you immediately, consider turning fsync off
first. That is something that I've noticed can speed up reproducing
issues like this. Although, I suspect you won't need to do that. I'm
using my standard development postgresql.conf, and so autovacuum was
disabled.
--
Peter Geoghegan
| Attachment | Content-Type | Size |
|---|---|---|
| toast-upsert-bug.script.pgbench | application/octet-stream | 6.7 KB |
| toast-upsert-bug.sh | application/x-sh | 248 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-06-29 05:13:22 | Re: BUG #14150: Attempted to delete invisible tuple |
| Previous Message | Дилян Палаузов | 2016-06-28 21:04:41 | Re: BUG #14217: Respect $CFLAGS from /usr/local/etc/config.site |