public inbox for [email protected]  
help / color / mirror / Atom feed
From: Laurenz Albe <[email protected]>
To: Boris Dovčík <[email protected]>
To: [email protected]
Subject: Re: Postgres 12 update to new major version
Date: Fri, 05 Jun 2026 23:59:20 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CALeMo=Ef44kKRZYVOjjdC70zBv8vj+YRi06DXTVA_sJHsqFTtw@mail.gmail.com>
References: <CALeMo=Ef44kKRZYVOjjdC70zBv8vj+YRi06DXTVA_sJHsqFTtw@mail.gmail.com>

On Fri, 2026-06-05 at 14:11 +0200, Boris Dovčík wrote:
> I have a question regarding the update of the production database (multiple TB of data)
> from version 12 to higher major version. We would like to jump to 15 or 16. DB is installed
> on a Linux server with one replica on another, it is not on cloud.
> 
> First question is should we perform updates one by one? 12 -> 13 -> 14 etc. or is it
> viable to jump to 16 right away? (We have few functions but usually its plain tables)

You can jump over versions, but you should not upgrade to an old release like v15 or
v16.  Go to v18 or better.  It looks like you are not too eager to upgrade frequently,
otherwise you would not be on v12 today.  So I recommend that you put the time when
the next upgrade will be necessary as far into the future as possible.

> Second we are contemplating options for the update since we are limited with downtime.
> We could get 4 hours of downtime for the whole update (either via pg_update or dumps).
> We are not sure how to estimate the time for direct update or dumps. What would be the
> recommended way for it?

You should use pg_upgrade --link.  Then the upgrade can be a matter of minutes, unless
you have lots and lots of tables, functions or large objects.

Yours,
Laurenz Albe






view thread (5+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Postgres 12 update to new major version
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox