Re: Order of InvokeObjectPostAlterHook within ATExecSetNotNull - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Order of InvokeObjectPostAlterHook within ATExecSetNotNull
Date
Msg-id 202603181633.32bikq5m7kh6@alvherre.pgsql
Whole thread Raw
In response to Order of InvokeObjectPostAlterHook within ATExecSetNotNull  (Artur Zakirov <zaartur@gmail.com>)
Responses Re: Order of InvokeObjectPostAlterHook within ATExecSetNotNull
List pgsql-hackers
On 2026-Mar-18, Artur Zakirov wrote:

> Hello hackers!
> 
> The commit 14e87ff added pg_constraint rows for not-null [1]. The
> consequence of the patch is that it changed the order of
> InvokeObjectPostAlterHook() call and update of "attnotnull" field in
> the catalog. Before the update was before the call of the hook [2].
> And now "attnotnull" is updated after the call of
> InvokeObjectPostAlterHook() [3].
> 
> This is a noticeable change to extensions which use
> "object_access_hook" since they see a bit of stale information about
> the attribute.
> 
> Is this an intended behavior or rather a bug?

This was not intentional.  Want to submit a patch?

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion?
Next
From: Masahiko Sawada
Date:
Subject: Re: Initial COPY of Logical Replication is too slow