Horton

Re: Fix publisher-side sequence permission reporting

Fujii Masao <masao.fujii@gmail.com>

View thread View on postgr.es
From: Fujii Masao <masao.fujii@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Tristan Partin <tristan@partin.io>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-07-08T09:19:44Z
Lists: pgsql-hackers 
On Thu, Jul 2, 2026 at 6:55 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> > How about something like this instead?
> >
> >     This function returns a row of NULL values if the specified relation
> >     OID does not exist, if it is not a sequence, if the current user lacks
> >     <literal>SELECT</literal> privilege on the sequence, if the sequence
> >     is another session's temporary sequence, or if it is an unlogged
> >     sequence on a standby server.
> >
>
> Sounds reasonable. But after this we don't need the next para to say:
> "It requires <literal>SELECT</literal> privilege on the sequence.".
> See attached.

Thanks for the patch! I've pushed it.

> > I've updated the patch furthermore. Attached.
> >
>
> LGTM.

Thanks for the review! I've pushed this as well.

Regards,

-- 
Fujii Masao

Commits

  1. Fix unlogged sequence corruption after standby promotion

  2. doc: Clarify pg_get_sequence_data() privileges and NULL results

  3. Fix misreporting of publisher sequence permissions during sync

  4. Introduce pg_sequence_read_tuple().