postgres.git / summary / log / commit / refs

commit    a36882ef94afe8a114cf5c2928b2cb9620ffd855
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Thu Jul 14 20:34:30 2022 +0000
First released in: 16.0, 10.22, 11.17, 12.12, 13.8, 14.5, 15.0

    pg_upgrade doc: mention that replication slots must be recreated
    
    Reported-by: Nikhil Shetty
    
    Discussion: https://postgr.es/m/CAFpL5Vxastip0Jei-K-=7cKXTg=5sahSe5g=om=x68NOX8+PUA@mail.gmail.com
    
    Backpatch-through: 10


 doc/src/sgml/ref/pgupgrade.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 86239922cc0..7d656af1da7 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -569,7 +569,8 @@ rsync --archive --delete --hard-links --size-only --no-inc-recursive /vol1/pg_tb
        Configure the servers for log shipping.  (You do not need to run
        <function>pg_start_backup()</function> and <function>pg_stop_backup()</function>
        or take a file system backup as the standbys are still synchronized
-       with the primary.)
+       with the primary.)  Replication slots are not copied and must
+       be recreated.
       </para>
      </step>
 


[parent: 846ae360ab2d]