Fix join-removal logic for pseudoconstant and outerjoin-delayed quals.
In these cases a qual can get marked with the removable rel in its
required_relids, but this is just to schedule its evaluation correctly, not
because it really depends on the rel. We were assuming that, in effect,
we could throw away *all* quals so marked, which is nonsense. Tighten up
the logic to be a little more paranoid about which quals belong to the
outer join being considered for removal, and arrange for all quals that
don't belong to be updated so they will still get evaluated correctly.
Also fix another problem that happened to be exposed by this test case,
which was that make_join_rel() was failing to notice some cases where
a constant-false qual could be used to prove a join relation empty. If it's
a pushed-down constant false, then the relation is empty even if it's an
outer join, because the qual applies after the outer join expansion.
Per report from Nathan Grange. Back-patch into 9.0.
joinrels.c (r1.105 -> r1.106)
analyzejoins.c (r1.3 -> r1.4)
joininfo.c (r1.52 -> r1.53)
joininfo.h (r1.38 -> r1.39)
join.out (r1.46 -> r1.47)
join.sql (r1.35 -> r1.36)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2010-09-14 23:15:37|
|Subject: pgsql: Fix join-removal logic for pseudoconstant and outerjoin-delayed |
|Previous:||From: Heikki Linnakangas||Date: 2010-09-14 13:35:14|
|Subject: pgsql: Oops, the timeout argument to WaitLatchOrSocket is in |