pg_upgrade question

From: Alan Stange <stange(at)rentec(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: pg_upgrade question
Date: 2021-12-02 16:05:50
Message-ID: bad5baeb-46e1-0b67-4d61-92693b6783aa@rentec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello all,

We're running a 13.x installation and looking to upgrade to 14.1.  This
is all on Linux servers.   We have a main instance running with a number
of hot standby replicas configured.   In the past, we have done a
dump/restore on a slow evening and then rsynced all the bits around so
that the main server and all replicas were identical at the start.   The
database has gotten larger now (~1TB) so that is a less desirable option.

So I am thinking to do a pg_upgrade --link on each of the main and the
hot standby replicas, and then restarting all the processes.   I'm sure
this will work fine on the main server, but I have not seen any mention
of this working in the expected way on the hot standby replicas.   Can
someone confirm that the steps I described here will work in the way I
am optimistically expecting it will?

I should mention that we are running on ZFS, and will take a snapshot
prior to the upgrade, so that if something goes sideways with our use of
--link  we can revert back instantly. 

Thank you,

Alan

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2021-12-02 16:10:07 Re: pg_upgrade question
Previous Message Gianni Ceccarelli 2021-12-02 14:04:04 Re: case insensitive collation of Greek's sigma