| From: | Maxim Orlov <m(dot)orlov(at)postgrespro(dot)ru> |
|---|---|
| To: | Greg Nancarrow <gregn4422(at)gmail(dot)com> |
| Cc: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Pengchengliu <pengchengliu(at)tju(dot)edu(dot)cn>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel scan with SubTransGetTopmostTransaction assert coredump |
| Date: | 2021-06-22 15:06:49 |
| Message-ID: | 08ae178b309c617a9701cbc7ed8a98f0@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The analysis in the beginning of the discussion seems to be right, but
the fix v2 looks too invasive for me.
Personally, I'd like not to remove snapshot even if transaction is
read-only. I propose to consider "xid < TransactionXmin" as a legit case
and just promote xid to TransactionXmin.
It's annoying this old bug still not fixed. What do you think?
---
Best regards,
Maxim Orlov.
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-PG14-Fix-parallel-worker-failed-assertion-and-coredump.patch | text/x-diff | 1.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-06-22 15:15:39 | Re: Maintaining a list of pgindent commits for "git blame" to ignore |
| Previous Message | Tom Lane | 2021-06-22 15:04:26 | Re: Maintaining a list of pgindent commits for "git blame" to ignore |