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

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Pierre Fortin <pf(at)pfortin(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade: can I use same binary for old & new?
Date: 2025-07-05 18:11:32
Message-ID: b558441b-0bd8-4cfb-aa4c-64fdcb530531@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

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?

> Thanks,
> Pierre
>
>
>
>
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2025-07-05 18:19:45 Re: pg_upgrade: can I use same binary for old & new?
Previous Message pf 2025-07-05 18:05:18 Re: pg_upgrade: can I use same binary for old & new?