Re: Safest pgupgrade jump distance

From: Justin Clift <justin(at)postgresql(dot)org>
To: Dávid Suchan <david(dot)suchan(dot)ds(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Safest pgupgrade jump distance
Date: 2024-02-12 10:15:31
Message-ID: 1a37201c2d8fb3c712baa45aaf325ce5@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dominique Devienne 2024-02-12 10:30:09 Re: How to do faster DML
Previous Message Dávid Suchan 2024-02-12 10:07:48 Safest pgupgrade jump distance