public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: pg_upgrade: can I use same binary for old & new?
Date: Sat, 5 Jul 2025 14:19:45 -0400
Message-ID: <CANzqJaCA_FA+e4kn5yqgSm=fc-cPrgFQocL12-45R-UUeEmwyQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On Sat, Jul 5, 2025 at 2:11 PM Adrian Klaver <[email protected]>
wrote:
> On 7/5/25 09:52, Pierre Fortin wrote:
> > Hi,
> >
> > [Hope this gets through after dumping DKIM-ignorant mail provider.]
> >
> > 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?
>
> > - even with ~70TB, I don't have enough contiguous disk space to
> > dump/restore
>
> What was the pg_dump command?
For something that big, he must have been doing an uncompressed plain
format dump instead of a directory/custom format dump. Maybe even added
--attribute-inserts too.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
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: pg_upgrade: can I use same binary for old & new?
In-Reply-To: <CANzqJaCA_FA+e4kn5yqgSm=fc-cPrgFQocL12-45R-UUeEmwyQ@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