On Tue, Jun 30, 2026 at 1:01 AM vignesh C <[email protected]> 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


Reply via email to