| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | grosser(dot)meister(dot)morti(at)gmx(dot)net |
| Subject: | BUG #18963: Column confupdsetcols missing in pg_catalog.pg_constraint |
| Date: | 2025-06-19 16:33:52 |
| Message-ID: | 18963-4fa37be61361c1d6@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18963
Logged by: Mathias Panzenböck
Email address: grosser(dot)meister(dot)morti(at)gmx(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-06-19 16:57:46 | Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. |
| Previous Message | Dilip Kumar | 2025-06-19 16:04:22 | Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. |