MIME-Version: 1.0
References: <20250705125207.31b4d475@pfortin.com> <b558441b-0bd8-4cfb-aa4c-64fdcb530531@aklaver.com>
 <20250705142416.06e99667@pfortin.com>
In-Reply-To: <20250705142416.06e99667@pfortin.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Sat, 5 Jul 2025 15:10:35 -0400
Message-ID: <CANzqJaBPjHBufQtcmHopcMNpR7VymJZZQXyijifD45vVrxcEog@mail.gmail.com>
Subject: Re: pg_upgrade: can I use same binary for old & new?
To: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000002b547e0639335eb3"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaBPjHBufQtcmHopcMNpR7VymJZZQXyijifD45vVrxcEog%40mail.gmail.com>
Precedence: bulk

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

On Sat, Jul 5, 2025 at 2:24=E2=80=AFPM <pf@pfortin.com> wrote:

> On Sat, 5 Jul 2025 11:11:32 -0700 Adrian Klaver wrote:
>
> >On 7/5/25 09:52, Pierre Fortin wrote:
>
> >> Wanting to upgrade from:
> >> PostgreSQL 15.13 on x86_64-mageia-linux-gnu,
> >> compiled by gcc (Mageia 15.1.0-1.mga10) 15.1.0, 64-bit
> >> to:
> >> PG 17.5
> >>
> >> Way back, I was able to use -k|--link option on pg_upgrade (PG13 to
> PG15);
> >> but since then:
> >>
> >> - my DB has grown to over 8TB
> >
> >How did you measure above?
>
> # du -sb /var/lib/pgsql/data
> 8227910662297   /var/lib/pgsql/data
>
> >> - even with ~70TB, I don't have enough contiguous disk space to
> >>    dump/restore
> >
> >What was the pg_dump command?
>
> Didn't try given:
> $ df /mnt/db
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/sdh1        17T   13T  3.0T  82% /mnt/db
>
> I suppose I could dump each of the 1408 objects to various available
> drives; but given my previous experience with PG13 to PG15 using --link
> which took seconds; I'm hoping to avoid wasting time (at my age, hours
> matter).
>

There's something you're not telling us.  The whole point of "pg_upgrade
--link" is an in-place upgrade. It might use a few extra GB of disk space
for when it backs up the PG15 schema and restores it to PG17.  Thus, why
are you complaining about running out of disk space?

--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

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

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Jul 5, 2025 at 2:24=E2=80=AFPM &l=
t;<a href=3D"mailto:pf@pfortin.com">pf@pfortin.com</a>&gt; wrote:</div><div=
 class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex">On Sat, 5 Jul 2025 11:11:32 -0700 Adrian Klaver wrote:<=
br>
<br>
&gt;On 7/5/25 09:52, Pierre Fortin wrote:<br>
<br>
&gt;&gt; Wanting to upgrade from:<br>
&gt;&gt; PostgreSQL 15.13 on x86_64-mageia-linux-gnu,<br>
&gt;&gt; compiled by gcc (Mageia 15.1.0-1.mga10) 15.1.0, 64-bit<br>
&gt;&gt; to:<br>
&gt;&gt; PG 17.5<br>
&gt;&gt; <br>
&gt;&gt; Way back, I was able to use -k|--link option on pg_upgrade (PG13 t=
o PG15);<br>
&gt;&gt; but since then:<br>
&gt;&gt; <br>
&gt;&gt; - my DB has grown to over 8TB=C2=A0 <br>
&gt;<br>
&gt;How did you measure above?<br>
<br>
# du -sb /var/lib/pgsql/data<br>
8227910662297=C2=A0 =C2=A0/var/lib/pgsql/data<br>
<br>
&gt;&gt; - even with ~70TB, I don&#39;t have enough contiguous disk space t=
o<br>
&gt;&gt;=C2=A0 =C2=A0 dump/restore=C2=A0 <br>
&gt;<br>
&gt;What was the pg_dump command?<br>
<br>
Didn&#39;t try given:<br>
$ df /mnt/db<br>
Filesystem=C2=A0 =C2=A0 =C2=A0 Size=C2=A0 Used Avail Use% Mounted on<br>
/dev/sdh1=C2=A0 =C2=A0 =C2=A0 =C2=A0 17T=C2=A0 =C2=A013T=C2=A0 3.0T=C2=A0 8=
2% /mnt/db<br>
<br>
I suppose I could dump each of the 1408 objects to various available<br>
drives; but given my previous experience with PG13 to PG15 using --link<br>
which took seconds; I&#39;m hoping to avoid wasting time (at my age, hours<=
br>
matter).<br></blockquote><div><br></div><div>There&#39;s=C2=A0something you=
&#39;re not telling=C2=A0us.=C2=A0 The whole point of &quot;pg_upgrade --li=
nk&quot; is an in-place upgrade. It might use a few extra GB of disk space =
for when it backs up the PG15 schema and restores it to PG17.=C2=A0 Thus, w=
hy are you complaining=C2=A0about running out of disk space?</div></div><di=
v><br></div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=
=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Death to &lt;Redacted&g=
t;, and butter sauce.<div>Don&#39;t boil me, I&#39;m still alive.<br><div><=
div>&lt;Redacted&gt; lobster!</div></div></div></div></div></div>

--0000000000002b547e0639335eb3--