pgsql: Fix error code for referential action RESTRICT

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix error code for referential action RESTRICT
Date: 2024-12-02 07:26:20
Message-ID: E1tI0p2-000huS-C3@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/086c84b23d99c2ad268f97508cd840efc1fdfd79

Modified Files
--------------
src/backend/utils/adt/ri_triggers.c | 32 +++++++++++++++++----
src/test/regress/expected/collate.icu.utf8.out | 4 +--
src/test/regress/expected/foreign_key.out | 16 +++++------
src/test/regress/expected/without_overlaps.out | 40 +++++++++++++-------------
4 files changed, 57 insertions(+), 35 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Dean Rasheed 2024-12-02 11:36:29 pgsql: Fix #include order in timestamp.c.
Previous Message Tom Lane 2024-12-01 19:16:05 pgsql: Fix broken list-munging in ecpg's remove_variables().