Disallow LATERAL references to the target table of an UPDATE/DELETE.
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 12 Jan 2014 00:03:12 +0000 (19:03 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 12 Jan 2014 00:03:12 +0000 (19:03 -0500)
commit158b7fa6a34006bdc70b515e14e120d3e896589b
tree4cc53f3251ed648fa2aaa4adc8afad52b7b1629b
parent910bac5953012198e210848660ea31f27ab08abc
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.
src/backend/parser/analyze.c
src/backend/parser/parse_relation.c
src/include/parser/parse_node.h
src/test/regress/expected/join.out
src/test/regress/sql/join.sql