| From: | Mathias Panzenböck <grosser(dot)meister(dot)morti(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint |
| Date: | 2025-06-20 20:35:40 |
| Message-ID: | 94185454-0d6f-489b-9dbe-65ddd81a3c48@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Am 20.06.25 um 17:14 schrieb Tom Lane:
> PG Bug reporting form <noreply(at)postgresql(dot)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#b7a607d6496828fd21caf2b6bd2b0f07
>
> regards, tom lane
I see. Thank you!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2025-06-20 20:41:16 | Re: Index Rebuild Bug fixed in 14.6.7 |
| Previous Message | Tom Lane | 2025-06-20 20:24:41 | Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist |