From: Mathias Panzenböck <grosser.meister.morti@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
Date: Fri, 20 Jun 2025 22:35:40 +0200
Message-ID: <94185454-0d6f-489b-9dbe-65ddd81a3c48@gmx.net> (raw)
In-Reply-To: <1939224.1750432499@sss.pgh.pa.us>
References: <18963-4fa37be61361c1d6@postgresql.org>
<1939224.1750432499@sss.pgh.pa.us>
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!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: grosser.meister.morti@gmx.net, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint
In-Reply-To: <94185454-0d6f-489b-9dbe-65ddd81a3c48@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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