From: Johannes Truschnigg <johannes@truschnigg.info>
To: Ghiurea, Isabella <Isabella.Ghiurea@nrc-cnrc.gc.ca>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: upgrade slave in streaming replication from PG 10.4 to 10.5.1
Date: Thu, 25 Oct 2018 20:07:30 +0200
Message-ID: <20181025180729.xoharwuuytno5b7j@vault.lan> (raw)
In-Reply-To: <1540479215718.82040@nrc-cnrc.gc.ca>
References: <1540479215718.82040@nrc-cnrc.gc.ca>
Hi Isabella,
On Thu, Oct 25, 2018 at 02:53:35PM +0000, Ghiurea, Isabella wrote:
> Gmorning List,
>
> we have a system running PG streaming replication using repmgr4 , PG hosts
> are running Cent OS 7 with PG 10.4, we have a request to upgrade to PG 10.5
> , my plan is to upgrade the slave db host first and later on /next month
> switch over and upgrade the existing PG master, we are using the following
> PG extensions: citext , pg_sphere,pg_stat_statements,pgrowlocks.
Your question reads to me as if you somehow missed the important change in
pg's version numbering scheme that 10.0 introduced: These days, 10.n to 10.n+1
is not considered a major release upgrade (of the sort that requires
pg_upgrade or dump+restore, etc.) any more; it's what (e.g.) 9.6.n to 9.6.n+1
used to be. Therefore, both versions you mentioned should be compatible and
allow physical replication between themselves, no matter if the master or the
slave are on the newer (minor) version than the other.
> Also in existing PG 10.4 cfg:/data/ pg_wal is a link and we have cfg
> multiple tablespaces
Shouldn't matter, if your existing configuration works. Just install the new,
upgraded binaries, restart your service(s), and you should be good to go.
Personally, I'd upgrade the slave first- if anything goes awry (very unlikely,
but accidents happen!), you don't have to fail over that way.
> Are any issues related to replication if we are upgrading the PG slave host first , ?
Not in this scenario - if you were doing an actual major release upgrade (10.x
to 11.x or later), you'd have to get more creative and (probably - there are
options, if you cannot afford that kind of interruption, but they are a bit
more involved) break replication for a while. If it comes to that, I'm sure
someone the list will be able to help out.
Cheers, and best of luck with your upgrade procedure!
--
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )
www: https://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp: johannes@truschnigg.info
Please do not bother me with HTML-email or attachments. Thank you.
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: johannes@truschnigg.info, Isabella.Ghiurea@nrc-cnrc.gc.ca
Subject: Re: upgrade slave in streaming replication from PG 10.4 to 10.5.1
In-Reply-To: <20181025180729.xoharwuuytno5b7j@vault.lan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox