diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2024-04-16 11:22:39 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2024-04-16 11:22:39 -0400 |
commit | f502849d49a4744a8b6ce8abaf7af7c320c4ea0b (patch) | |
tree | d4c73d9c443f0f8506e5e684107347dbd3da73b4 /src/backend/executor/nodeModifyTable.c | |
parent | 4b0e5d6012918de2069a2636aacf60bbc6c0085c (diff) | |
download | postgresql-f502849d49a4744a8b6ce8abaf7af7c320c4ea0b.tar.gz postgresql-f502849d49a4744a8b6ce8abaf7af7c320c4ea0b.zip |
Fix generation of EC join conditions at the wrong plan level.
get_baserel_parampathinfo previously assumed without checking that
the results of generate_join_implied_equalities "necessarily satisfy
join_clause_is_movable_into". This turns out to be wrong in the
presence of outer joins, because the generated clauses could include
Vars that mustn't be evaluated below a relevant outer join. That
led to applying clauses at the wrong plan level and possibly getting
incorrect query results. We must check each clause's nullable_relids,
and really the right thing to do is test join_clause_is_movable_into.
However, trying to fix it that way exposes an oversight in
equivclass.c: it wasn't careful about marking join clauses for
appendrel children with the correct clause_relids. That caused the
modified get_baserel_parampathinfo code to reject some clauses it
still needs to accept. (See parallel commit for HEAD/v16 for more
commentary about that.)
Per bug #18429 from BenoƮt Ryder. This misbehavior existed for
a long time before commit 2489d76c4, so patch v12-v15 this way.
Discussion: https://postgr.es/m/18429-8982d4a348cc86c6@postgresql.org
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions