public inbox for [email protected]
help / color / mirror / Atom feedBUG #19464: Server crash (SIGABRT) with UPDATE containing multiple multi-column assignments
5+ messages / 3 participants
[nested] [flat]
* BUG #19464: Server crash (SIGABRT) with UPDATE containing multiple multi-column assignments
@ 2026-04-20 09:45 PG Bug reporting form <[email protected]>
0 siblings, 1 reply; 5+ messages in thread
From: PG Bug reporting form @ 2026-04-20 09:45 UTC (permalink / raw)
To: [email protected]; +Cc: [email protected]
The following bug has been logged on the website:
Bug reference: 19464
Logged by: chunling qin
Email address: [email protected]
PostgreSQL version: 14.0
Operating system: centos
Description:
This issue could not be reproduced with the latest version, but we can
easily reproduced by PostgreSQL 14devel. I am submitting this report for
official confirmation.
postgres=# CREATE TABLE t1 (a int, b int);
UPDATE t1
SET (a) = (SELECT 1), -- subquery single-column assignment
b = 2, -- single-column assignment
(a) = ROW(1); ERROR: relation "t1" already exists
postgres=# postgres=# postgres-# postgres-# postgres-#
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.
postgres=#
postgres=# select version();
version
--------------------------------------------------------------------------------------
-------------------------------------------------
PostgreSQL 14devel on x86_64-pc-linux-gnu, compiled by clang version 17.0.6
(TencentO
S 17.0.6-8.tl4.ap.2), 64-bit (commit:86dc90056d)
(1 row)
Minimal Reproduction:
```
CREATE TABLE t1 (a int, b int);
UPDATE t1
SET (a) = (SELECT 1), -- subquery single-column assignment
b = 2, -- single-column assignment
(a) = ROW(1); -- ROW constructor single-column assignment
```
Crash Summary
The server terminates with SIGABRT due to a failed assertion:
TRAP: FailedAssertion("pstate->p_multiassign_exprs == NIL", File:
"parse_target.c",
Line: 277, PID: 2398140)
Version
- Git commit: 86dc90056dfdbd9d1b891718d2e5614e3e432f35
- Version string: PostgreSQL 14devel (commit 86dc90056d, "Rework planning
and
execution of UPDATE and DELETE.")
- Platform: x86_64-pc-linux-gnu, compiled by clang 17.0.6, 64-bit
- Build config: enable_debug=yes, CFLAGS includes -g -O0, asserts enabled
Full Backtrace
#0 __pthread_kill_implementation () from /lib64/libc.so.6
#1 raise () from /lib64/libc.so.6
#2 abort () from /lib64/libc.so.6
#3 ExceptionalCondition (conditionName="pstate->p_multiassign_exprs ==
NIL",
errorType="FailedAssertion",
fileName="parse_target.c", lineNumber=277)
at assert.c:69
#4 transformExpressionList (pstate=..., exprlist=...,
exprKind=EXPR_KIND_UPDATE_SOURCE,
allowDefault=true)
at parse_target.c:277
#5 transformRowExpr (pstate=..., r=..., allowDefault=true)
at parse_expr.c:2086
#6 transformMultiAssignRef (pstate=..., maref=...)
at parse_expr.c:1454
#7 transformExprRecurse (pstate=..., expr=...)
at parse_expr.c:212
#8 transformExpr (pstate=..., expr=..., exprKind=EXPR_KIND_UPDATE_SOURCE)
at parse_expr.c:104
#9 transformTargetEntry (pstate=..., node=..., ...)
at parse_target.c:95
#10 transformTargetList (pstate=..., targetlist=...,
exprKind=EXPR_KIND_UPDATE_SOURCE)
at parse_target.c:183
#11 transformUpdateTargetList (pstate=..., origTlist=...)
at analyze.c:2308
#12 transformUpdateStmt (pstate=..., stmt=...)
at analyze.c:2283
#13 transformStmt (pstate=..., parseTree=...)
at analyze.c:295
#14 transformOptionalSelectInto (pstate=..., parseTree=...)
at analyze.c:250
#15 transformTopLevelStmt (pstate=..., parseTree=...)
at analyze.c:200
#16 parse_analyze (parseTree=..., sourceText="UPDATE t1 SET (a) = (SELECT
1), b = 2,
(a) = ROW(1);", ...)
at analyze.c:120
#17 pg_analyze_and_rewrite (...)
at postgres.c:637
#18 exec_simple_query (query_string="UPDATE t1 SET (a) = (SELECT 1), b =
2, (a) =
ROW(1);")
at postgres.c:1101
#19 PostgresMain (...)
at postgres.c:4415
#20 main (argc=5, argv=...)
at main.c:205
^ permalink raw reply [nested|flat] 5+ messages in thread
* RE: BUG #19464: Server crash (SIGABRT) with UPDATE containing multiple multi-column assignments
@ 2026-04-21 12:20 Hayato Kuroda (Fujitsu) <[email protected]>
parent: PG Bug reporting form <[email protected]>
0 siblings, 1 reply; 5+ messages in thread
From: Hayato Kuroda (Fujitsu) @ 2026-04-21 12:20 UTC (permalink / raw)
To: [email protected] <[email protected]>; [email protected] <[email protected]>
Dear Chunling,
Thanks for reporting issues.
> This issue could not be reproduced with the latest version, but we can
> easily reproduced by PostgreSQL 14devel. I am submitting this report for
> official confirmation.
To confirm, can it happen on the latest PG14 (14.22)? It's the old development
version which should not be used. Same things can be said for other reports.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
^ permalink raw reply [nested|flat] 5+ messages in thread
* =?gb18030?B?u9i4tKO6UkU6IEJVRyAjMTk0NjQ6IFNlcnZlciBj?= =?gb18030?B?cmFzaCAoU0lHQUJSVCkgd2l0aCBVUERBVEUgY29u?= =?gb18030?B?dGFpbmluZyBtdWx0aXBsZSAgICBtdWx0aS1jb2x1?= =?gb18030?B?bW4gYXNzaWdubWVudHM=?=
@ 2026-04-21 12:35 =?gb18030?B?t8nT4w==?= <[email protected]>
parent: Hayato Kuroda (Fujitsu) <[email protected]>
0 siblings, 1 reply; 5+ messages in thread
From: =?gb18030?B?t8nT4w==?= @ 2026-04-21 12:35 UTC (permalink / raw)
To: =?gb18030?B?SGF5YXRvIEt1cm9kYSAoRnVqaXRzdSk=?= <[email protected]>; =?gb18030?B?cGdzcWwtYnVnc0BsaXN0cy5wb3N0Z3Jlc3FsLm9yZw==?= <[email protected]>
Hi Developer,
Thanks for the reply. I have verified this on PG 14.22 and can confirm that the issue is not reproducible on 14.22—it returns the expected error:
ERROR: multiple assignments to same column "a"
Best regards,
Chunling
------------------ 原始邮件 ------------------
发件人: "Hayato Kuroda (Fujitsu)" <[email protected]>;
发送时间: 2026年4月21日(星期二) 晚上8:20
收件人: "飞鱼"<[email protected]>;"[email protected]"<[email protected]>;
主题: RE: BUG #19464: Server crash (SIGABRT) with UPDATE containing multiple multi-column assignments
Dear Chunling,
Thanks for reporting issues.
> This issue could not be reproduced with the latest version, but we can
> easily reproduced by PostgreSQL 14devel. I am submitting this report for
> official confirmation.
To confirm, can it happen on the latest PG14 (14.22)? It's the old development
version which should not be used. Same things can be said for other reports.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
^ permalink raw reply [nested|flat] 5+ messages in thread
* RE: 回复：RE: BUG #19464: Server crash (SIGABRT) with UPDATE containing multiple multi-column assignments
@ 2026-04-21 13:00 Hayato Kuroda (Fujitsu) <[email protected]>
parent: =?gb18030?B?t8nT4w==?= <[email protected]>
0 siblings, 1 reply; 5+ messages in thread
From: Hayato Kuroda (Fujitsu) @ 2026-04-21 13:00 UTC (permalink / raw)
To: '飞鱼' <[email protected]>; +Cc: [email protected] <[email protected]>
Dear 飞鱼,
Thanks for the quick confirmation. I suggest you to confirm the same for other reports [1], [2] and [3].
[1]: https://www.postgresql.org/message-id/19461-8d03395b71f86664%40postgresql.org
[2]: https://www.postgresql.org/message-id/19462-563c85bec169995a%40postgresql.org
[3]: https://www.postgresql.org/message-id/19463-f59d5d2a41969756%40postgresql.org
Best regards,
Hayato Kuroda
FUJITSU LIMITED
^ permalink raw reply [nested|flat] 5+ messages in thread
* =?gb18030?B?u9i4tKO6UkU6ILvYuLSjulJFOiBCVUcgIzE5NDY0?= =?gb18030?B?OiBTZXJ2ZXIgY3Jhc2ggKFNJR0FCUlQpIHdpdGgg?= =?gb18030?B?VVBEQVRFIGNvbnRhaW5pbmcgbXVsdGlwbGUgICAg?= =?gb18030?B?bXVsdGktY29sdW1uIGFzc2lnbm1lbnRz?=
@ 2026-04-21 13:11 =?gb18030?B?t8nT4w==?= <[email protected]>
parent: Hayato Kuroda (Fujitsu) <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: =?gb18030?B?t8nT4w==?= @ 2026-04-21 13:11 UTC (permalink / raw)
To: =?gb18030?B?SGF5YXRvIEt1cm9kYSAoRnVqaXRzdSk=?= <[email protected]>; +Cc: =?gb18030?B?cGdzcWwtYnVnc0BsaXN0cy5wb3N0Z3Jlc3FsLm9yZw==?= <[email protected]>
Hi Developer,
Thanks for the quick reply. I have also verified the other three bugs on PG 15.17, and none of them are reproducible either. These issues appear to be specific to the build environment based on merge commit 7103ebb7aa and update commit 86dc9005, which is the exact version I used for commit-level testing. They seem to be tied to the transient state of the code at that particular commit—subsequent releases likely fixed or refactored the relevant code paths.
Best regards,
Chunling
------------------ 原始邮件 ------------------
发件人: "Hayato Kuroda (Fujitsu)" <[email protected]>;
发送时间: 2026年4月21日(星期二) 晚上9:00
收件人: "飞鱼"<[email protected]>;
抄送: "[email protected]"<[email protected]>;
主题: RE: 回复：RE: BUG #19464: Server crash (SIGABRT) with UPDATE containing multiple multi-column assignments
Dear 飞鱼,
Thanks for the quick confirmation. I suggest you to confirm the same for other reports [1], [2] and [3].
[1]: https://www.postgresql.org/message-id/19461-8d03395b71f86664%40postgresql.org
[2]: https://www.postgresql.org/message-id/19462-563c85bec169995a%40postgresql.org
[3]: https://www.postgresql.org/message-id/19463-f59d5d2a41969756%40postgresql.org
Best regards,
Hayato Kuroda
FUJITSU LIMITED
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2026-04-21 13:11 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-04-20 09:45 BUG #19464: Server crash (SIGABRT) with UPDATE containing multiple multi-column assignments PG Bug reporting form <[email protected]>
2026-04-21 12:20 ` Hayato Kuroda (Fujitsu) <[email protected]>
2026-04-21 12:35 ` =?gb18030?B?u9i4tKO6UkU6IEJVRyAjMTk0NjQ6IFNlcnZlciBj?= =?gb18030?B?cmFzaCAoU0lHQUJSVCkgd2l0aCBVUERBVEUgY29u?= =?gb18030?B?dGFpbmluZyBtdWx0aXBsZSAgICBtdWx0aS1jb2x1?= =?gb18030?B?bW4gYXNzaWdubWVudHM=?= =?gb18030?B?t8nT4w==?= <[email protected]>
2026-04-21 13:00 ` RE: 回复：RE: BUG #19464: Server crash (SIGABRT) with UPDATE containing multiple multi-column assignments Hayato Kuroda (Fujitsu) <[email protected]>
2026-04-21 13:11 ` =?gb18030?B?u9i4tKO6UkU6ILvYuLSjulJFOiBCVUcgIzE5NDY0?= =?gb18030?B?OiBTZXJ2ZXIgY3Jhc2ggKFNJR0FCUlQpIHdpdGgg?= =?gb18030?B?VVBEQVRFIGNvbnRhaW5pbmcgbXVsdGlwbGUgICAg?= =?gb18030?B?bXVsdGktY29sdW1uIGFzc2lnbm1lbnRz?= =?gb18030?B?t8nT4w==?= <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox