From afa7eba400b593e2a73a5fd618e510cef571aee7 Mon Sep 17 00:00:00 2001
From: Peter Smith <peter.b.smith@fujitsu.com>
Date: Thu, 2 Jul 2026 14:48:43 +1200
Subject: [PATCH v1] DOCS - clarify that REFRESH SEQUENCES might be using stale
 publication data

---
 doc/src/sgml/ref/alter_subscription.sgml | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/alter_subscription.sgml b/doc/src/sgml/ref/alter_subscription.sgml
index e4f0b6b16c7..c9ed7745554 100644
--- a/doc/src/sgml/ref/alter_subscription.sgml
+++ b/doc/src/sgml/ref/alter_subscription.sgml
@@ -236,13 +236,19 @@ ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable> RENAME TO <
     <listitem>
      <para>
       Re-synchronize sequence data with the publisher. Unlike
-      <link linkend="sql-altersubscription-params-refresh-publication">
-      <command>ALTER SUBSCRIPTION ... REFRESH PUBLICATION</command></link> which
+      <literal>REFRESH PUBLICATION</literal> which
       only has the ability to synchronize newly added sequences,
       <literal>REFRESH SEQUENCES</literal> will re-synchronize the sequence
       data for all currently subscribed sequences. It does not add or remove
       sequences from the subscription to match the publication.
      </para>
+     <para>
+      If the publication's sequence membership has changed,
+      <link linkend="sql-altersubscription-params-refresh-publication">
+      <command>ALTER SUBSCRIPTION ... REFRESH PUBLICATION</command></link>
+      should be run before <literal>REFRESH SEQUENCES</literal> to ensure the
+      subscription's known sequence list is current.
+     </para>
      <para>
       See <xref linkend="sequence-definition-mismatches"/> for
       recommendations on how to handle any warnings about sequence definition
-- 
2.47.3