projects / users / hanada / postgres.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 974c5a8) | patch
In a nestloop inner indexscan, it's OK to use pushed-down baserestrictinfo
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 6 Dec 2005 16:50:36 +0000 (16:50 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 6 Dec 2005 16:50:36 +0000 (16:50 +0000)
commit953208a34cbb7585ed4ae782141052461d35739b
treea2b85d5791d1af2037878eddfe1a14c61edbe232tree
parent974c5a87309294c81054bd7ade736cbdf8066bb7commit | diff
In a nestloop inner indexscan, it's OK to use pushed-down baserestrictinfo
clauses even if it's an outer join.  This is a corner case since such
clauses could only arise from weird OUTER JOIN ON conditions, but worth
fixing.  Per example from Ron at cheapcomplexdevices.com.
src/backend/optimizer/path/indxpath.c diff | blob | blame | history
Hanada's development tree.