postgres.git / summary / log / commit / refs

commit    f1780eaf485320eebdcdb98dcc8fd187fba27f25
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Tue Sep 26 22:54:10 2023 +0000

    doc: pg_upgrade, clarify standby servers must remain running
    
    Also mention that mismatching primary/standby LSNs should never
    happen.
    
    Reported-by: Nikolay Samokhvalov
    
    Discussion: https://postgr.es/m/CAM527d8heqkjG5VrvjU3Xjsqxg41ufUyabD9QZccdAxnpbRH-Q@mail.gmail.com
    
    Backpatch-through: 11


 doc/src/sgml/ref/pgupgrade.sgml | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 98662102fa7..d401053edf3 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -354,8 +354,8 @@ NET STOP postgresql-&majorversion;
     </para>
 
     <para>
-     Streaming replication and log-shipping standby servers can
-     remain running until a later step.
+     Streaming replication and log-shipping standby servers must be
+     running during this shutdown so they receive all changes.
     </para>
    </step>
 
@@ -368,8 +368,6 @@ NET STOP postgresql-&majorversion;
      servers are caught up by running <application>pg_controldata</application>
      against the old primary and standby clusters.  Verify that the
      <quote>Latest checkpoint location</quote> values match in all clusters.
-     (There will be a mismatch if old standby servers were shut down
-     before the old primary or if the old standby servers are still running.)
      Also, make sure <varname>wal_level</varname> is not set to
      <literal>minimal</literal> in the <filename>postgresql.conf</filename> file on the
      new primary cluster.


[parent: 28919a063d8c]