diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2024-12-02 08:18:36 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2024-12-02 08:22:34 +0100 |
| commit | 086c84b23d99c2ad268f97508cd840efc1fdfd79 (patch) | |
| tree | acb02f9dbcb9c51d6079934e2d6d8552a345410a /src/backend/utils/adt/timestamp.c | |
| parent | 2f696453d2b39fea800d5f7d8e5d3e1a2266de24 (diff) | |
| download | postgresql-086c84b23d99c2ad268f97508cd840efc1fdfd79.tar.gz postgresql-086c84b23d99c2ad268f97508cd840efc1fdfd79.zip | |
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
Diffstat (limited to 'src/backend/utils/adt/timestamp.c')
0 files changed, 0 insertions, 0 deletions