re: There is also nonstandard behavior if BEFORE triggers modify rows or
prevent updates during an update that is caused by a referential
action. This can lead to constraint violations or stored data that
does not honor the referential constraint.
That supports the position that it was already documented, I'll grant you
that. It is clearly a bug if it causes foreign key constraints to be
violated, documented or not. Otherwise foreign key constraints mean nothing
in PostgreSQL.
I don't think this would be particularly difficult to fix so that it causes
the statement to fail when there is a referential action, rather than
silently returning and leaving the database in an inconsistent state.
What is the argument in favor of retaining behavior that renders foreign
keys meaningless?
What is the process for deciding whether a report represents an actionable
bug that ought to be fixed by the community?
/Jim
-----
Jim Finnerty, AWS, Amazon Aurora PostgreSQL
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html
