Re: [HACKERS] Clarification in pg10'spgupgrade.html step 10 (upgrading standby servers) - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Clarification in pg10'spgupgrade.html step 10 (upgrading standby servers)
Date
Msg-id 20170913030632.GF6766@momjian.us
Whole thread Raw
In response to Re: [HACKERS] Clarification in pg10'spgupgrade.html step 10 (upgrading standby servers)  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Tue, Sep 12, 2017 at 07:54:15PM -0400, Stephen Frost wrote:
> Andreas,
> 
> * Andreas Joseph Krogh (andreas@visena.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@momjian.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 +


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [HACKERS] WAL logging problem in 9.4.3?
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] psql: new help related to variables are not too readable