On Tue, Jul 10, 2012 at 12:04:50PM -0400, Tom Lane wrote:
> Bruce Momjian <br...@momjian.us> writes:
> > + While a Log-Shipping Standby Server (<xref linkend="warm-standby">) can
> > + be upgraded, the server must be in changed to a primary server to allow
> > + writes, and after the upgrade it cannot be reused as a standby server.
> > + (Running <command>rsync</> after the upgrade allows reuse.)
>
> "in changed"? This sentence makes no sense at all to me.
Oops. New wording attached with "in" removed:
the server must be changed to a primary server
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
new file mode 100644
index 30f4544..04dffbf
*** a/doc/src/sgml/pgupgrade.sgml
--- b/doc/src/sgml/pgupgrade.sgml
*************** psql --username postgres --file script.s
*** 518,523 ****
--- 518,530 ----
</para>
<para>
+ While a Log-Shipping Standby Server (<xref linkend="warm-standby">) can
+ be upgraded, the server must be changed to a primary server to allow
+ writes, and after the upgrade it cannot be reused as a standby server.
+ (Running <command>rsync</> after the upgrade allows reuse.)
+ </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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
