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

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints
Date: 2025-03-25 13:39:17
Message-ID: ae8b8d27-e2e0-4214-8869-31e480801e1c@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 25.03.25 12:52, Alvaro Herrera wrote:
> 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.

done

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2025-03-25 14:11:20 Re: AIO v2.5
Previous Message Noah Misch 2025-03-25 13:33:21 Re: AIO v2.5