Tom Lane 27ff4cfe76 Disallow LATERAL references to the target table of an UPDATE/DELETE. ... On second thought, commit 0c051c9008 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.		2014-01-11 19:03:15 -05:00
..
examples	Update copyrights for 2013	2013-01-01 17:15:01 -05:00
isolation	Don't ignore tuple locks propagated by our updates	2013-12-18 13:31:27 -03:00
locale	Run newly-configured perltidy script on Perl files.	2012-07-04 21:47:49 -04:00
mb	Lots of doc corrections.	2012-04-23 22:43:09 -04:00
performance	Run newly-configured perltidy script on Perl files.	2012-07-04 21:47:49 -04:00
regress	Disallow LATERAL references to the target table of an UPDATE/DELETE.	2014-01-11 19:03:15 -05:00
thread	Update copyrights for 2013	2013-01-01 17:15:01 -05:00
Makefile	Add isolation test to check-world and installcheck-world	2012-03-05 20:19:20 +02:00