Horton

Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Suraj Kharage <suraj.kharage@enterprisedb.com>, jian he <jian.universality@gmail.com>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-03-25T11:52:08Z
Lists: 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

Commits

  1. Small fixes for Add ALTER TABLE ... ALTER CONSTRAINT ... SET [NO] INHERIT

  2. Add ALTER TABLE ... ALTER CONSTRAINT ... SET [NO] INHERIT

  3. Add pg_constraint rows for not-null constraints