projects / users / heikki / postgres.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2da2d34) | patch
Back out prior patch and instead just suppress SubqueryScan elimination
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 5 Sep 2005 18:59:38 +0000 (18:59 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 5 Sep 2005 18:59:38 +0000 (18:59 +0000)
commite35e6b1c37c1e52e36218dd3d35a5a2df1f4813f
treeba935d7a43e9f644081ac88efb6b5382954d8093tree
parent2da2d347706f0d8408f8d6b7a10be29286c911b7commit | diff
Back out prior patch and instead just suppress SubqueryScan elimination
when there are extra resjunk columns in the child node.  I found some
additional cases involving Append nodes that weren't handled by the
prior patch, and it's not clear how to fix them in the same way without
breaking inheritance cases.  So the prudent path seems to be to narrow
the scope of the optimization.
src/backend/optimizer/plan/setrefs.c diff | blob | blame | history
Heikki's random PostgreSQL patches