Re: Fix publisher-side sequence permission reporting

Fujii Masao <masao.fujii@gmail.com>

From: Fujii Masao <masao.fujii@gmail.com>

To: vignesh C <vignesh21@gmail.com>

Cc: Amit Kapila <amit.kapila16@gmail.com>, Tristan Partin <tristan@partin.io>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-06-29T23:55:57Z

Lists: pgsql-hackers

On Tue, Jun 30, 2026 at 1:01 AM vignesh C <vignesh21@gmail.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

Commits

Fix unlogged sequence corruption after standby promotion
- d2980067bc3b 15 (unreleased) landed
- 913d3b610ccd 16 (unreleased) landed
- a1ed6a9a031a 17 (unreleased) landed
- 627605713074 18 (unreleased) landed
- 22af34b98362 19 (unreleased) landed
- 8e684ce11dda master landed
doc: Clarify pg_get_sequence_data() privileges and NULL results
- 031904048aa2 19 (unreleased) landed
Fix misreporting of publisher sequence permissions during sync
- d4a657b0a4db 19 (unreleased) landed
Introduce pg_sequence_read_tuple().
- c8b06bb969bf 18.0 cited