projects / users / gsingh / postgres.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: edae280) | 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:46 +0000 (16:50 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 6 Dec 2005 16:50:46 +0000 (16:50 +0000)
commit386f0e50ef6bc29dcd3ccc8283e91a210be22899
tree55020619589650c9d508a7a39111a25825784b02tree
parentedae280e6993fa064e3e6106e96c50a64a025930commit | 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
Postgres clone for personal branches