aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/constraint.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-08-09 00:48:58 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-08-09 00:48:58 -0400
commit028a0c5a2913f18c954845cc014786912f39fa30 (patch)
treef25494a06c7364d50d206e27f9ad303ad6ec2434 /src/backend/commands/constraint.c
parent8956231576f082bd6e75f6c2f1c2a250b919176f (diff)
downloadpostgresql-028a0c5a2913f18c954845cc014786912f39fa30.tar.gz
postgresql-028a0c5a2913f18c954845cc014786912f39fa30.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/commands/constraint.c')
0 files changed, 0 insertions, 0 deletions