| commit | d641b827af3966e349cbcc592bc51a4ab770c37b | |
| author | Tom Lane <tgl@sss.pgh.pa.us> | |
| Wed, 10 Jan 2024 18:36:33 +0000 (10 13:36 -0500) | ||
| committer | Tom Lane <tgl@sss.pgh.pa.us> | |
| Wed, 10 Jan 2024 18:36:33 +0000 (10 13:36 -0500) | ||
| tree | a88f1c4638da20498785c334505491b1264323a9 | treesnapshot (tar.gz zip) |
| parent | 5b2da240e01ecaef8181b0feebaeb69e6fefdaa0 | commitdiff |
Handle WindowClause.runCondition in tree walker/mutator functions.
Commit 9d9c02ccd, which added the notion of a "run condition" for
window functions, neglected to teach nodeFuncs.c to process the new
field. Remarkably, that doesn't seem to have had any ill effects
before we invented Var.varnullingrels, but now it can cause visible
failures in join-removal scenarios.
I have no faith that there's not reachable problems in v15 too,
so back-patch the code change to v15 where 9d9c02ccd came in.
The test case seems irrelevant to v15, though.
Per bug #18277 from Zuming Jiang. Diagnosis and patch by
Richard Guo.
Discussion: https://postgr.es/m/18277-089ead83b329a2fd@postgresql.org
Commit 9d9c02ccd, which added the notion of a "run condition" for
window functions, neglected to teach nodeFuncs.c to process the new
field. Remarkably, that doesn't seem to have had any ill effects
before we invented Var.varnullingrels, but now it can cause visible
failures in join-removal scenarios.
I have no faith that there's not reachable problems in v15 too,
so back-patch the code change to v15 where 9d9c02ccd came in.
The test case seems irrelevant to v15, though.
Per bug #18277 from Zuming Jiang. Diagnosis and patch by
Richard Guo.
Discussion: https://postgr.es/m/18277-089ead83b329a2fd@postgresql.org
| src/backend/nodes/nodeFuncs.c | diffblobblamehistory | |
| src/test/regress/expected/window.out | diffblobblamehistory | |
| src/test/regress/sql/window.sql | diffblobblamehistory |