diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2025-01-16 20:40:07 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2025-01-16 20:40:07 -0500 |
| commit | bf826ea062979da02395fb2e8961feeef47604da (patch) | |
| tree | 3af3c8aa5b19badb814b7403e7922ebc50b967b5 /src/backend/executor | |
| parent | f7a8fc10ccb882249f8624b937f2c3b467d07bd6 (diff) | |
| download | postgresql-bf826ea062979da02395fb2e8961feeef47604da.tar.gz postgresql-bf826ea062979da02395fb2e8961feeef47604da.zip | |
Fix setrefs.c's failure to do expression processing on prune steps.
We should run the expression subtrees of PartitionedRelPruneInfo
structs through fix_scan_expr. Failure to do so means that
AlternativeSubPlans within those expressions won't be cleaned up
properly, resulting in "unrecognized node type" errors since v14.
It seems fairly likely that at least some of the other steps done
by fix_scan_expr are important here as well, resulting in as-yet-
undetected bugs. Therefore, I've chosen to back-patch this to
all supported branches including v13, even though the known
symptom doesn't manifest in v13.
Per bug #18778 from Alexander Lakhin.
Discussion: https://postgr.es/m/18778-24cd399df6c806af@postgresql.org
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions