MIME-Version: 1.0
From: Durumdara <durumdara@gmail.com>
Date: Thu, 1 May 2025 15:06:22 +0200
Message-ID: <CAEcMXh=PtUgwj5exvV8PpyvY0H=eOtUkn-wAPcn7p35vkeHzmg@mail.gmail.com>
Subject: Upgrading PG11 to PG17 without dump/restore
To: Postgres General <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000e40096063412b35c"
Archived-At: <https://www.postgresql.org/message-id/CAEcMXh%3DPtUgwj5exvV8PpyvY0H%3DeOtUkn-wAPcn7p35vkeHzmg%40mail.gmail.com>
Precedence: bulk

--000000000000e40096063412b35c
Content-Type: text/plain; charset="UTF-8"

Hello!

There is a heavily used server, with older debian, and PG11.
The data is more than 1,2 TB.
The PG_Upgrade is not possible because of lesser space and too old debian.

As we see now we have only one way to move this server.
1.) Installing a new server with actual debian.
2.) Installing the newest PG (17) on it.
3.) Stop work on one database. Dump it in the old, restore it in the new
and start the work with that. So we can move them one by one.

But this seems to be very hard, because we need to do this through an
internet connection, and the data is too much.

I have a question about it - is there a better way to do this?

For example we make a new cluster element (a read only slave) with newest
debian/PG, and use it to move the data in the background (replication).
And then we rename it to master. But I don't know if it's possible or not.
Maybe the slaves must be the same version as the master.

The main problem is that debian is too old, and we are afraid to use
PG_Upgrade because of too many version differences (11 < 17).

But maybe you have some good advice, how to do this with less complication.
Users can tolerate short downtimes, but not longer ones.

Thank you!

Best regards
dd

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

<div dir=3D"ltr">Hello!<br><br>There is a heavily used server, with older d=
ebian, and PG11.<div>The data is more than 1,2 TB.</div><div>The PG_Upgrade=
 is not possible because of lesser space and too old debian.</div><div><br>=
</div><div>As we see now we have only one way to move this server.</div><di=
v>1.) Installing a new server with actual debian.</div><div>2.) Installing =
the newest PG (17) on it.</div><div>3.) Stop work on one database. Dump it =
in the old, restore it in the new and start the work with that. So we can m=
ove them one by one.</div><div><br></div><div>But this seems to be very har=
d, because we need to do this through an internet connection, and the data =
is too much.</div><div><br></div><div>I have a question about it - is there=
 a better way to do this?</div><div><br></div><div>For=C2=A0example we make=
 a new cluster element (a read only slave) with newest debian/PG, and use i=
t to move the data in the background (replication).<br>And then we rename i=
t to master. But I don&#39;t know if it&#39;s possible or not.</div><div>Ma=
ybe the slaves must be the same version as the master.</div><div><br></div>=
<div>The main problem is that debian is too old, and we are afraid to use P=
G_Upgrade=C2=A0because of too many version differences=C2=A0(11 &lt; 17).</=
div><div><br></div><div>But maybe you have some good advice, how to do this=
 with less complication.</div>Users can tolerate short downtimes, but not l=
onger ones.<div><br></div><div>Thank you!</div><div><br></div><div>Best reg=
ards</div><div>dd<br><div><br></div></div></div>

--000000000000e40096063412b35c--