projects / users / hanada / postgres.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8b20f8a) | 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:59:22 +0000 (16:59 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 6 Dec 2005 16:59:22 +0000 (16:59 +0000)
commita025aa179c4ca15915ea2c523894faa31b2ca2f9
tree9260b2f6ff08b91953c34d7aa6f0ef8b611be72btree
parent8b20f8a51deef702047cf2d6c1872de37644205acommit | 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.