| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction |
| Date: | 2021-07-27 11:17:00 |
| Message-ID: | CA+hUKGKNQc9q+bUMyYWVKAuKgtrS-aY-AW0V1vzYm6FkMnYFqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jul 27, 2021 at 8:00 AM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> Thanks! I'm not sure, whether this is related to the fix, but my
> parallel installcheck script (attached) catches another assert with the
> patch applied:
> #2 0x000055b16d72aa32 in ExceptionalCondition (
> conditionName=conditionName(at)entry=0x55b16d89ccd0
> "!SxactIsPartiallyReleased(MySerializableXact)",
> errorType=errorType(at)entry=0x55b16d78301d "FailedAssertion",
> fileName=fileName(at)entry=0x55b16d89bbc9 "predicate.c",
> lineNumber=lineNumber(at)entry=4859) at assert.c:67
Reproduced here using a similar approach. It doesn't fail with this
new draft patch. The main thing I have learned is that
serializable-parallel-2.sql isn't really testing a very interesting
code path. I'll try to come up with a better test.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Fix-assertion-failures-in-parallel-SSI.patch | text/x-patch | 6.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Orishich Aleksey | 2021-07-27 11:38:20 | RE: Postgresql12: ERROR: Could not read from file "pg_act/02 F 4" at offset 253952: read too few bytes |
| Previous Message | Andrey V. Lepikhov | 2021-07-27 11:00:39 | Re: The case when AsyncAppend exists also in the qual of Async ForeignScan |