BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
The following bug has been logged on the website:
Bug reference: 18963
Logged by: Mathias Panzenböck
Email address: grosser.meister.morti@gmx.net
PostgreSQL version: 17.0
Operating system: Linux
Description:
Foreign key constraints have the option to list the columns that should be
changed in ON DELETE/ON UPDATE SET NULL/SET DEFAULT. For the ON DELETE case
these columns can be inspected with pg_catalog.pg_constraint.confdelsetcols,
but there is no such column for the ON UPDATE case. Is this an oversight?
There are also other constraint parameters that I couldn't find (NULLS
DISTINCT for UNIQUE constraints and index_parametrs for several kind of
constraints), but I haven't searched too long for those yet.
PG Bug reporting form <noreply@postgresql.org> writes:
Foreign key constraints have the option to list the columns that should be
changed in ON DELETE/ON UPDATE SET NULL/SET DEFAULT. For the ON DELETE case
these columns can be inspected with pg_catalog.pg_constraint.confdelsetcols,
but there is no such column for the ON UPDATE case. Is this an oversight?
It's intentional, see here:
/messages/by-id/85f8fcae-5a85-0d81-ae72-12c8a5cb271e@enterprisedb.com
regards, tom lane
Am 20.06.25 um 17:14 schrieb Tom Lane:
PG Bug reporting form <noreply@postgresql.org> writes:
Foreign key constraints have the option to list the columns that should be
changed in ON DELETE/ON UPDATE SET NULL/SET DEFAULT. For the ON DELETE case
these columns can be inspected with pg_catalog.pg_constraint.confdelsetcols,
but there is no such column for the ON UPDATE case. Is this an oversight?It's intentional, see here:
/messages/by-id/85f8fcae-5a85-0d81-ae72-12c8a5cb271e@enterprisedb.com
regards, tom lane
I see. Thank you!