Fix buggy interaction between array subscripts and subplan params
Andres Freund <andres@anarazel.de>
Fix buggy interaction between array subscripts and subplan params In a7f107df2 I changed subplan param evaluation to happen within the containing expression. As part of that, ExecInitSubPlanExpr() was changed to evaluate parameters via a new EEOP_PARAM_SET expression step. These parameters were temporarily stored into ExprState->resvalue/resnull, with some reasoning why that would be fine. Unfortunately, that analysis was wrong - ExecInitSubscriptionRef() evaluates the input array into "resv"/"resnull", which will often point to ExprState->resvalue/resnull. This means that the EEOP_PARAM_SET, if inside an array subscript, would overwrite the input array to array subscript. The fix is fairly simple - instead of evaluating into ExprState->resvalue/resnull, store the temporary result of the subplan in the subplan's return value. Bug: #19370 Reported-by: Zepeng Zhang <redraiment@gmail.com> Diagnosed-by: Tom Lane <tgl@sss.pgh.pa.us> Diagnosed-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/19370-7fb7a5854b7618f1@postgresql.org Backpatch-through: 18
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/executor/execExpr.c | modified | +10 −8 |
| src/backend/executor/execExprInterp.c | modified | +3 −3 |
| src/test/regress/expected/subselect.out | modified | +17 −0 |
| src/test/regress/sql/subselect.sql | modified | +11 −0 |
Discussion
- BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression 9 messages · 2026-01-06 → 2026-01-07