public inbox for [email protected]  

help / color / mirror / Atom feed

From: Boris Dovčík <[email protected]>
To: [email protected]
Subject: Postgres 12 update to new major version
Date: Fri, 5 Jun 2026 14:11:12 +0200
Message-ID: <CALeMo=Ef44kKRZYVOjjdC70zBv8vj+YRi06DXTVA_sJHsqFTtw@mail.gmail.com> (raw)

Hello all,

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)

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?

One option we see could be logical replication to the new major version on
a new machine, but we received feedback that in our setup it might not be
recommendable. Does it make sense to try logical replica? What would be the
downsides of it?

Best regards,
Boris Dovčík

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]
  Subject: Re: Postgres 12 update to new major version
  In-Reply-To: <CALeMo=Ef44kKRZYVOjjdC70zBv8vj+YRi06DXTVA_sJHsqFTtw@mail.gmail.com>

* 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