Re: Safest pgupgrade jump distance - Mailing list pgsql-general

From Justin Clift
Subject Re: Safest pgupgrade jump distance
Date
Msg-id 1a37201c2d8fb3c712baa45aaf325ce5@postgresql.org
Whole thread Raw
In response to Safest pgupgrade jump distance  (Dávid Suchan <david.suchan.ds@gmail.com>)
List pgsql-general
On 2024-02-12 20:07, Dávid Suchan wrote:
> Hi, I was wondering what is the safest pg_upgrade version upgrade 
> distance
> going from 9.6 version. Do I need to go version by version or I can go 
> from
> 9.6 to 15? We have a very huge database(TBs) with one replication 
> server,
> so we will first run the pgupgrade on the main server and then rsync to 
> a
> standby replica. I'm not sure whether it's safe to do it from 9.6 to 15 
> at
> once, I have tested the process on 9,6 to 10 yet. Would that be a wise
> approach to such an upgrade of the db?
> Also, when upgrading a very big database with replication where none of 
> the
> data can be allowed to be lost, is the pgupgrade into rsync approach 
> the
> best one? Thanks.

pgupgrade from 9.6 directly to 16 should work fine.  That's part of the
test suite for one of my side projects (pgautoupgrade in Docker).

You'll probably want to use the "--link" option too, so it uses the 
existing
data files rather than recreating them.  It's *much* faster. :)

I'm not sure how the rsync of things will figure into it though.  If 
you're
just rsyncing files when the database is turned off, it should be 
straight
forward.

As always though, make sure you have a backup (that's known to work) 
before
you try it all out though. :)

+ Justin



pgsql-general by date:

Previous
From: Dávid Suchan
Date:
Subject: Safest pgupgrade jump distance
Next
From: Dominique Devienne
Date:
Subject: Re: How to do faster DML