]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8178871) | 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:55 +0000 (16:50 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 6 Dec 2005 16:50:55 +0000 (16:50 +0000)
commit7563a16b116603db2c986b04883e18af6dda2be2
tree081dd3c2fa3ed1767daec7c7b15983fe48506812tree | snapshot
parent81788719b9f24e58960665230c68bde36e098e03commit | 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 | history
Unnamed repository; edit this file 'description' to name the repository.