Date: Sat, 5 Jul 2025 14:24:16 -0400
Feedback-ID: :pf@pfortin.com:pfortin.com:flockmailId
From: pf@pfortin.com
To: pgsql-general@lists.postgresql.org
Subject: Re: pg_upgrade: can I use same binary for old & new?
Message-ID: <20250705142416.06e99667@pfortin.com>
In-Reply-To: <b558441b-0bd8-4cfb-aa4c-64fdcb530531@aklaver.com>
References: <20250705125207.31b4d475@pfortin.com>
	<b558441b-0bd8-4cfb-aa4c-64fdcb530531@aklaver.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/20250705142416.06e99667%40pfortin.com>
Precedence: bulk

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).

Cheers,
Pierre