aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xlogutils.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-01-11 19:03:15 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2014-01-11 19:03:15 -0500
commit27ff4cfe760a79c78eac2948cea67f2ae486cbbf (patch)
treef47dc4f947ed95b08bb0c1bdb8f5bdd2e16ed8b3 /src/backend/access/transam/xlogutils.c
parent5bfcc9ec5e78733c5770c17d43c0315e0fcc14b9 (diff)
downloadpostgresql-27ff4cfe760a79c78eac2948cea67f2ae486cbbf.tar.gz
postgresql-27ff4cfe760a79c78eac2948cea67f2ae486cbbf.zip
Disallow LATERAL references to the target table of an UPDATE/DELETE.
On second thought, commit 0c051c90082da0b7e5bcaf9aabcbd4f361137cdc was over-hasty: rather than allowing this case, we ought to reject it for now. That leaves the field clear for a future feature that allows the target table to be re-specified in the FROM (or USING) clause, which will enable left-joining the target table to something else. We can then also allow LATERAL references to such an explicitly re-specified target table. But allowing them right now will create ambiguities or worse for such a feature, and it isn't something we documented 9.3 as supporting. While at it, add a convenience subroutine to avoid having several copies of the ereport for disalllowed-LATERAL-reference cases.
Diffstat (limited to 'src/backend/access/transam/xlogutils.c')
0 files changed, 0 insertions, 0 deletions