On Tue, Jul 10, 2012 at 06:29:24PM +0200, Magnus Hagander wrote: > > Testing maybe? I feel we have just avoided saying what you can and > > can't do with the standbys and pg_upgrade, so I think we have to state > > something. If we just want to say "recreate", let's say that. > > Well, the bottom line is we can'd do *anything* with a standby with > pg_upgrade. > > Once you've promoted it, it is no longer a standby, and now you can > use pg_upgrade. > > >> And I think the sentence about running rsync is extremely vague - run > >> rsync where and how? What are you actually trying to suggest people > >> do? > > > > Updated docs attached. > > I suggest just removing the rsync part completely. You're basically > saying "you ca nset up a new standby after you're done", which is kind > of obvious anyway. And if you're going to use rsync fromthe master to > make a new standby, there's no point in running pg_upgrade on the new > standby in the first place.
I went the other direction and just said you can't upgrade a standby (as a standby), and to just use rsync --- patch attached. -- 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..4a646bd *** a/doc/src/sgml/pgupgrade.sgml --- b/doc/src/sgml/pgupgrade.sgml *************** psql --username postgres --file script.s *** 518,523 **** --- 518,529 ---- </para> <para> + A Log-Shipping Standby Server (<xref linkend="warm-standby">) cannot + be upgraded because the server must allow writes. The simplest case + is to upgrade the primary and use rsync to upgrade the standbys. + </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 (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers