pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
3+ messages / 3 participants
[nested] [flat]

* BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
@ 2025-06-19 16:33  PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 1 reply; 3+ messages in thread

From: PG Bug reporting form @ 2025-06-19 16:33 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: grosser.meister.morti@gmx.net

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.



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
@ 2025-06-20 15:14  Tom Lane <tgl@sss.pgh.pa.us>
  parent: PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2025-06-20 15:14 UTC (permalink / raw)
  To: grosser.meister.morti@gmx.net; +Cc: pgsql-bugs@lists.postgresql.org

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:

https://www.postgresql.org/message-id/flat/85f8fcae-5a85-0d81-ae72-12c8a5cb271e%40enterprisedb.com#b...

			regards, tom lane





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
@ 2025-06-20 20:35  Mathias Panzenböck <grosser.meister.morti@gmx.net>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 3+ messages in thread

From: Mathias Panzenböck @ 2025-06-20 20:35 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-bugs@lists.postgresql.org

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:
> 
> https://www.postgresql.org/message-id/flat/85f8fcae-5a85-0d81-ae72-12c8a5cb271e%40enterprisedb.com#b...
> 
> 			regards, tom lane

I see. Thank you!





^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2025-06-20 20:35 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-06-19 16:33 BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint PG Bug reporting form <noreply@postgresql.org>
2025-06-20 15:14 ` Tom Lane <tgl@sss.pgh.pa.us>
2025-06-20 20:35   ` Mathias Panzenböck <grosser.meister.morti@gmx.net>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox