Re: Order of InvokeObjectPostAlterHook within ATExecSetNotNull

Artur Zakirov <zaartur@gmail.com>

View thread View on postgr.es

From: Artur Zakirov <zaartur@gmail.com>

To: Álvaro Herrera <alvherre@kurilemu.de>

Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-03-18T16:55:25Z

Lists: pgsql-hackers

Attachments

object_access_hook_attnotnull_order_18.patch (application/octet-stream) patch
object_access_hook_attnotnull_order.patch (application/octet-stream) patch

On Wed, 18 Mar 2026 at 17:34, Álvaro Herrera <alvherre@kurilemu.de> wrote:
> >
> > 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/

Thank you for the quick response. Sure, I attached the patch for the
main branch and for REL_18_STABLE just in case, although the main
patch also should apply to REL_18_STABLE.
I think we might need to backpatch it to PG 18 too where the change
was introduced.

-- 
Kind regards,
Artur

Commits

SET NOT NULL: Call object-alter hook only after the catalog change
- e7975f1c06b5 19 (unreleased) landed
- 6958077ceb93 18.4 landed
Add pg_constraint rows for not-null constraints
- 14e87ffa5c54 18.0 cited