| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | vignesh C <vignesh21(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tristan Partin <tristan(at)partin(dot)io>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix publisher-side sequence permission reporting |
| Date: | 2026-06-29 23:55:57 |
| Message-ID: | CAHGQGwGLkNs_FSiW3hbc+K5DF066wpJfoYiS0sq8v3ettzBRkA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 30, 2026 at 1:01 AM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> Thanks for the updated patches. I verified that the issue occurs with
> nextval() on all supported branches up to v15, where unlogged
> sequences are available. The corresponding back patches apply cleanly
> to their respective branches and fix the issue. I also checked other
> unlogged objects but couldn't reproduce a similar issue with them.
>
> Overall, the patches look good to me.
Thanks for the review! I've pushed the patch.
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Henson Choi | 2026-06-30 00:07:11 | Re: Row pattern recognition |
| Previous Message | David G. Johnston | 2026-06-29 23:42:21 | Re: PostgreSQL select-only CTE removal is too aggressive? |