summaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/drop_user_mapping.sgml
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-09-14 23:15:37 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-09-14 23:15:37 +0000
commitbab9f1d585b15db59ec2703adaadc3efcf3f1810 (patch)
treeb3832fd84974f3c91a9e4c45e07849b13bb5ba93 /doc/src/sgml/ref/drop_user_mapping.sgml
parent105faeb3569b83a2bb2a6b6e367b77d1c51c1789 (diff)
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.
Diffstat (limited to 'doc/src/sgml/ref/drop_user_mapping.sgml')
0 files changed, 0 insertions, 0 deletions