Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints
Date
Msg-id 202503251152.brshiuib7dfw@alvherre.pgsql
Whole thread Raw
In response to Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints
List pgsql-hackers
Hello

On 2025-Mar-25, Peter Eisentraut wrote:

> A patch in the NOT ENFORCED constraints patch series proposes to refactor
> some of the code added by this patch series ([0] patch v18-0001).  I noticed
> that the code paths from this patch series do not call
> InvokeObjectPostAlterHook() or CacheInvalidateRelcache() when a constraint
> is altered.  Was this intentional?  If not, I can fix it as part of that
> other patch, just wanted to check here.

It was not, I'm good with you fixing it, with thanks.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"The ability of users to misuse tools is, of course, legendary" (David Steele)
https://postgr.es/m/11b38a96-6ded-4668-b772-40f992132797@pgmasters.net



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Reducing memory consumed by RestrictInfo list translations in partitionwise join planning
Next
From: Ashutosh Bapat
Date:
Subject: Re: Enhance 'pg_createsubscriber' to retrieve databases automatically when no database is provided.