From: Bruce Momjian <bruce@momjian.us>
To: vignesh C <vignesh21@gmail.com>
Cc: rh@vonng.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Fix sequence membership command in PG19 release notes
Date: Mon, 26 Oct 2026 23:17:12 -0400
Message-ID: <auAXuMcMFgcF2aTc@momjian.us> (raw)
In-Reply-To: <CALDaNm1agomELtDDqdF4KnAp6s6nKBMjU7VpmKQGh_o69XQTkg@mail.gmail.com>
References: <BF65B113-46A1-40F4-A4B0-76E90EFD7F00@vonng.com>
<CALDaNm1agomELtDDqdF4KnAp6s6nKBMjU7VpmKQGh_o69XQTkg@mail.gmail.com>
On Thu, Oct 22, 2026 at 09:28:31PM +0530, vignesh C wrote:
> On Fri, 16 Oct 2026 at 17:03, <rh@vonng.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@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
Attachments:REL_19_STABLE.diff (text/x-diff, 1.1K) downloaddiff --git a/doc/src/sgml/release-19.sgml b/doc/src/sgml/release-19.sgmlindex 7d723995575..12704e568b1 100644--- a/doc/src/sgml/release-19.sgml+++ b/doc/src/sgml/release-19.sgml@@ -1542,8 +1542,7 @@ Allow sequence values stored in subscribers to match the publisher (Vignesh C)
</para>
<para>
-This is enabled during <link linkend="sql-createsubscription"><command>CREATE SUBSCRIPTION</command></link>, <link linkend="sql-altersubscription"><command>ALTER SUBSCRIPTION ... REFRESH PUBLICATION</command></link>, and <link linkend="sql-altersubscription"><command>ALTER SUBSCRIPTION ... REFRESH SEQUENCES</command></link>. The latter only updates values, not sequence-existence. Function <link linkend="func-pg-get-sequence-data"><function>pg_get_sequence_data()</function></link> allows inspection of sequence synchronization.+This is enabled during <link linkend="sql-altersubscription"><command>ALTER SUBSCRIPTION ... [ADD|SET|REFRESH|DROP] PUBLICATION</command></link>. Function <link linkend="func-pg-get-sequence-data"><function>pg_get_sequence_data()</function></link> allows inspection of sequence synchronization.
</para>
</listitem>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, vignesh21@gmail.com, rh@vonng.com, pgsql-docs@lists.postgresql.org
Subject: Re: Fix sequence membership command in PG19 release notes
In-Reply-To: <auAXuMcMFgcF2aTc@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox