Re: Fix publisher-side sequence permission reporting - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Fix publisher-side sequence permission reporting
Date
Msg-id CAHGQGwE9AOvhqPOx7J=zPug5s90FhNVPH8m0m3AVJVzjG8npBQ@mail.gmail.com
Whole thread
In response to Re: Fix publisher-side sequence permission reporting  (vignesh C <vignesh21@gmail.com>)
Responses Re: Fix publisher-side sequence permission reporting
List pgsql-hackers
On Wed, Jun 24, 2026 at 7:49 PM vignesh C <vignesh21@gmail.com> wrote:
> Thanks for the patch. I verified that it fixes the issue with reading
> unlogged sequences on a promoted standby.

Thanks for testing!


> Do you think it would be worthwhile to add a test for this scenario,
> or do you feel the additional test is not necessary in this case?

I think it's worth adding a test for this scenario, so I've added one to
the patch. The test uses nextval() to read the unlogged sequence
instead of pg_get_sequence_data(), since this patch needs to be
backpatched to v15, while pg_get_sequence_data() was introduced in
v19.

Attached are updated patches for master and the stable branches.

Regards,

--
Fujii Masao

Attachment

pgsql-hackers by date:

Previous
From: Nitin Jadhav
Date:
Subject: Re: Change checkpoint‑record‑missing PANIC to FATAL
Next
From: Amit Kapila
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication