| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Andreas Joseph Krogh <andreas(at)visena(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers) |
| Date: | 2017-09-13 03:06:32 |
| Message-ID: | 20170913030632.GF6766@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 12, 2017 at 07:54:15PM -0400, Stephen Frost wrote:
> Andreas,
>
> * Andreas Joseph Krogh (andreas(at)visena(dot)com) wrote:
> > I have to ask; Why not run pg_upgrade on standby, after verifying that it's in
> > sync with primary and promoting it to primary if necessary and then making it
> > standby again after pg_upgrade is finished?
>
> I don't think that we could be guaranteed that the catalog tables would
> be the same on the replica as on the primary if they were actually
> created by pg_upgrade.
FYI, the other problem is that standby can't go into write mode or it
would diverge from the primary.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-09-13 03:39:37 | Re: psql: new help related to variables are not too readable |
| Previous Message | Thomas Munro | 2017-09-13 03:05:31 | Re: WAL logging problem in 9.4.3? |