aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-09-05 18:59:38 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-09-05 18:59:38 +0000
commite35e6b1c37c1e52e36218dd3d35a5a2df1f4813f (patch)
treeba935d7a43e9f644081ac88efb6b5382954d8093 /src/backend/access/gist
parent2da2d347706f0d8408f8d6b7a10be29286c911b7 (diff)
downloadpostgresql-e35e6b1c37c1e52e36218dd3d35a5a2df1f4813f.tar.gz
postgresql-e35e6b1c37c1e52e36218dd3d35a5a2df1f4813f.zip
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.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions