Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xLXgZ-00000001ZHO-4Bju for pgsql-docs@arkaria.postgresql.org; Tue, 27 Oct 2026 03:17:16 +0000 Received: from localhost ([127.0.0.1]:46464 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xLXgZ-00000008s6M-2KeT for pgsql-docs@arkaria.postgresql.org; Tue, 27 Oct 2026 03:17:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]:47924) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xLXgZ-00000008s6E-1O9A for pgsql-docs@lists.postgresql.org; Tue, 27 Oct 2026 03:17:15 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xLXgX-000000017RZ-2IaR for pgsql-docs@lists.postgresql.org; Tue, 27 Oct 2026 03:17:14 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=AWOdzH6LreMGTwfF1PRN4nIV5Q1tPQgUQIx88SHt80Y=; b=Q0Nis eYFrTxLlLFqTv+6PLD+/NfDBMnpyDwKFnREBmNQQgMT0/H5wv7mhkzKmFXzbarJPMiBsN7+SfkFfs Afkx3VwEEdkDKgS3PmFLXKSomB4kQS1dFSpT/Bk21oEhPN1dVKCvtw2jC3N+gp8ONq6qF80/y6oTV YO7juL1GDBQT3x8/CUlg85SvOfwKrmhHwr51uht55O1vtTrDaCPdvKmenJ5LA4hrPm9N6a2s9EM8f nE0GUetcVonmyNrGfYUO0IbWEb14y8a8p7wCLMxzPOmNM/aqkZ9jOUfERk3H4LeUQ8rf82STEGImL z+hVEcOxG7Qu0eGV9MwlZ+rJ3fFFA==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1xLXgW-00000003SOn-1sVR; Mon, 26 Oct 2026 23:17:12 -0400 Date: Mon, 26 Oct 2026 23:17:12 -0400 From: Bruce Momjian To: vignesh C Cc: rh@vonng.com, pgsql-docs@lists.postgresql.org Subject: Re: Fix sequence membership command in PG19 release notes Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="itEXCkT7cUFKNwTn" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --itEXCkT7cUFKNwTn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Oct 22, 2026 at 09:28:31PM +0530, vignesh C wrote: > On Fri, 16 Oct 2026 at 17:03, 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 https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future. --itEXCkT7cUFKNwTn Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="REL_19_STABLE.diff" diff --git a/doc/src/sgml/release-19.sgml b/doc/src/sgml/release-19.sgml index 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) -This is enabled during CREATE SUBSCRIPTION, ALTER SUBSCRIPTION ... REFRESH PUBLICATION, and ALTER SUBSCRIPTION ... REFRESH SEQUENCES. The latter only updates values, not sequence -existence. Function pg_get_sequence_data() allows inspection of sequence synchronization. +This is enabled during ALTER SUBSCRIPTION ... [ADD|SET|REFRESH|DROP] PUBLICATION. Function pg_get_sequence_data() allows inspection of sequence synchronization. --itEXCkT7cUFKNwTn--