Re: pg_upgrade: can I use same binary for old & new?

On Sat, Jul 5, 2025 at 2:11 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
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!