Feedback-ID: i76984098:Fastmail
Message-ID: <b558441b-0bd8-4cfb-aa4c-64fdcb530531@aklaver.com>
Date: Sat, 5 Jul 2025 11:11:32 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: pg_upgrade: can I use same binary for old & new?
To: Pierre Fortin <pf@pfortin.com>, pgsql-general@lists.postgresql.org
References: <20250705125207.31b4d475@pfortin.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <20250705125207.31b4d475@pfortin.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/b558441b-0bd8-4cfb-aa4c-64fdcb530531%40aklaver.com>
Precedence: bulk

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.klaver@aklaver.com