MIME-Version: 1.0
From: =?UTF-8?B?Qm9yaXMgRG92xI3DrWs=?= <bdovcik@gmail.com>
Date: Fri, 5 Jun 2026 14:11:12 +0200
Message-ID: 
 <CALeMo=Ef44kKRZYVOjjdC70zBv8vj+YRi06DXTVA_sJHsqFTtw@mail.gmail.com>
Subject: Postgres 12 update to new major version
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000003a8fdc0653808ff7"
Archived-At: 
 <https://www.postgresql.org/message-id/CALeMo%3DEf44kKRZYVOjjdC70zBv8vj%2BYRi06DXTVA_sJHsqFTtw%40mail.gmail.com>
Precedence: bulk

--0000000000003a8fdc0653808ff7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=C4=8D=C3=ADk

--0000000000003a8fdc0653808ff7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello all,</div><div><br></div><div>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 cl=
oud.</div><div><br></div><div>First question is should we perform=C2=A0upda=
tes one by one? 12 -&gt; 13 -&gt; 14 etc. or is it viable=C2=A0to jump to 1=
6 right away? (We have few functions but usually its plain tables)</div><di=
v><br></div><div>Second we are contemplating=C2=A0options for the update si=
nce 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 estima=
te the time for direct update or dumps. What would be the recommended way f=
or it?</div><div><br></div><div>One option we see could be logical replicat=
ion to the new major version on a new machine, but we received=C2=A0feedbac=
k that in our setup it might not be recommendable. Does it make sense to tr=
y logical replica? What would be the downsides of it?</div><div><br></div><=
div>Best regards,</div><div>Boris Dov=C4=8D=C3=ADk</div></div>

--0000000000003a8fdc0653808ff7--