| From: | Artur Zakirov <zaartur(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Order of InvokeObjectPostAlterHook within ATExecSetNotNull |
| Date: | 2026-03-18 16:55:25 |
| Message-ID: | CAKNkYnzAKjibTv4HVPxY4FgPp7W0cX2zToo+DjUF93CLMMq6Sg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 18 Mar 2026 at 17:34, Álvaro Herrera <alvherre(at)kurilemu(dot)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
| Attachment | Content-Type | Size |
|---|---|---|
| object_access_hook_attnotnull_order_18.patch | application/octet-stream | 786 bytes |
| object_access_hook_attnotnull_order.patch | application/octet-stream | 786 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2026-03-18 16:59:11 | Re: Don't synchronously wait for already-in-progress IO in read stream |
| Previous Message | Jacob Champion | 2026-03-18 16:47:14 | Re: unclear OAuth error message |