pg_upgrade.diff

text/x-diff

Filename: pg_upgrade.diff

Type: text/x-diff

Part: 0

Message: Re: Using pg_upgrade on log-shipping standby servers

Patch

Same data as JSON: GET /api/v1/attachments/:id/patch the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes. API reference →

Format: unified

File	+	−
doc/src/sgml/pgupgrade.sgml	0	0

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
new file mode 100644
index 30f4544..623276a
*** a/doc/src/sgml/pgupgrade.sgml
--- b/doc/src/sgml/pgupgrade.sgml
*************** psql --username postgres --file script.s
*** 518,523 ****
--- 518,531 ----
    </para>
  
    <para>
+    While a Log-Shipping Standby Server (<xref linkend="warm-standby">) can
+    be upgraded, the server must be promoted to a primary server to allow
+    writes, and after the upgrade it cannot be reused as a standby server.
+    You can run <command>rsync</> after the upgrade to guarantee all the
+    files are identical, and then the former standby can be reused.
+   </para>
+ 
+   <para>
     If you want to use link mode and you do not want your old cluster
     to be modified when the new cluster is started, make a copy of the
     old cluster and upgrade that in link mode. To make a valid copy