Tom Lane 2c535bfe81 Fix incorrect optimization of foreign-key checks. When an UPDATE on the ... referencing table does not change the tuple's FK column(s), we don't bother to check the PK table since the constraint was presumably already valid. However, the check is still necessary if the tuple was inserted by our own transaction, since in that case the INSERT trigger will conclude it need not make the check (since its version of the tuple has been deleted). We got this right for simple cases, but not when the insert and update are in different subtransactions of the current top-level transaction; in such cases the FK check would never be made at all. (Hence, problem dates back to 8.0 when subtransactions were added --- it's actually the subtransaction version of a bug fixed in 7.3.5.) Fix, and add regression test cases. Report and fix by Affan Salman.		2007-07-17 17:45:28 +00:00
..
bench	Update CVS HEAD for 2007 copyright. Back branches are typically not	2007-01-05 22:20:05 +00:00
examples	Wording cleanup for error messages. Also change can't -> cannot.	2007-02-01 19:10:30 +00:00
locale	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00
mb	Change the backend to reject strings containing invalidly-encoded multibyte	2006-05-21 20:05:21 +00:00
performance	Add CVS tag lines to files that were lacking them.	2006-03-11 04:38:42 +00:00
regress	Fix incorrect optimization of foreign-key checks. When an UPDATE on the	2007-07-17 17:45:28 +00:00
thread	Wording cleanup for error messages. Also change can't -> cannot.	2007-02-01 19:10:30 +00:00
Makefile	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00