Re: Fix sequence membership command in PG19 release notes

On Thu, Oct 22, 2026 at 09:28:31PM +0530, vignesh C wrote:
> On Fri, 16 Oct 2026 at 17:03, <rh(at)vonng(dot)com> wrote:
> >
> > The PG19 release-note entry about synchronizing sequence membership [1]
> > attributes that operation to REFRESH SEQUENCES. It should refer to
> > REFRESH PUBLICATION.
> >
> > REFRESH PUBLICATION adds and removes sequence entries in
> > pg_subscription_rel. REFRESH SEQUENCES instead resets existing sequence
> > entries to INIT for value resynchronization, without changing which
> > sequences are subscribed.
> >
> > This matches the ALTER SUBSCRIPTION reference [2] and the documentation
> > clarification committed as 19fbb47ef685 [3]. That commit did not update
> > release-19.sgml.
> >
> > The attached one-line patch changes the command name in that sentence.
> > It is based on REL_19_STABLE at a66ab9a9d382 and passes git apply --check.
>
> Thanks for the patch, one suggestion, how about we mention something like:
> This is done by REFRESH PUBLICATION and by ADD PUBLICATION, DROP
> PUBLICATION, and SET PUBLICATION, which add newly published sequences
> to the subscription and remove dropped ones. REFRESH SEQUENCES does
> not change which sequences are subscribed.

Okay, I have applied the attached patch based on your instructions. Let
me know if I need to change anything.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.