Fix error code for referential action RESTRICT
authorPeter Eisentraut <peter@eisentraut.org>
Mon, 2 Dec 2024 07:18:36 +0000 (08:18 +0100)
committerPeter Eisentraut <peter@eisentraut.org>
Mon, 2 Dec 2024 07:22:34 +0000 (08:22 +0100)
commit086c84b23d99c2ad268f97508cd840efc1fdfd79
treeacb02f9dbcb9c51d6079934e2d6d8552a345410a
parent2f696453d2b39fea800d5f7d8e5d3e1a2266de24
Fix error code for referential action RESTRICT

According to the SQL standard, if the referential action RESTRICT is
triggered, it has its own error code.  We previously didn't use that,
we just used the error code for foreign key violation.  But RESTRICT
is not necessarily an actual foreign key violation.  The foreign key
might still be satisfied in theory afterwards, but the RESTRICT
setting prevents the action even then.  So it's a separate kind of
error condition.

Discussion: https://www.postgresql.org/message-id/ea5b2777-266a-46fa-852f-6fca6ec480ad@eisentraut.org
src/backend/utils/adt/ri_triggers.c
src/test/regress/expected/collate.icu.utf8.out
src/test/regress/expected/foreign_key.out
src/test/regress/expected/without_overlaps.out