diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-08-09 00:49:11 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-08-09 00:49:11 -0400 |
commit | ceaf5052c6a7bee794211f5d4c503639bdf3dff0 (patch) | |
tree | b39dd9e4872497eff2214649835593558d1858b0 /src/backend/access/gist/gistvacuum.c | |
parent | 0a6167f76bc4e3a433d097ba0c39f843e66c669f (diff) | |
download | postgresql-ceaf5052c6a7bee794211f5d4c503639bdf3dff0.tar.gz postgresql-ceaf5052c6a7bee794211f5d4c503639bdf3dff0.zip |
Fix nested PlaceHolderVar expressions that appear only in targetlists.
A PlaceHolderVar's expression might contain another, lower-level
PlaceHolderVar. If the outer PlaceHolderVar is used, the inner one
certainly will be also, and so we have to make sure that both of them get
into the placeholder_list with correct ph_may_need values during the
initial pre-scan of the query (before deconstruct_jointree starts).
We did this correctly for PlaceHolderVars appearing in the query quals,
but overlooked the issue for those appearing in the top-level targetlist;
with the result that nested placeholders referenced only in the targetlist
did not work correctly, as illustrated in bug #6154.
While at it, add some error checking to find_placeholder_info to ensure
that we don't try to create new placeholders after it's too late to do so;
they have to all be created before deconstruct_jointree starts.
Back-patch to 8.4 where the PlaceHolderVar mechanism was introduced.
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions