Re: Order of InvokeObjectPostAlterHook within ATExecSetNotNull
Álvaro Herrera <alvherre@kurilemu.de>
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Artur Zakirov <zaartur@gmail.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-03-20T13:45:29Z
Lists: pgsql-hackers
On 2026-Mar-18, Artur Zakirov wrote: > 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. Thanks, this is clearly my mistake -- pushed to both branches. (I didn't use the patch you sent for 18, just the one for master, which I then cherry-picked into 18. I would say that it's not necessary to submit a version specific to a branch when the one for master cherry-picks cleanly.) -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
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