Re: pg_upgrade: can I use same binary for old & new? - Mailing list pgsql-general

From Pierre Fortin
Subject Re: pg_upgrade: can I use same binary for old & new?
Date
Msg-id 20250705171155.1c857f82@pfortin.com
Whole thread Raw
In response to Re: pg_upgrade: can I use same binary for old & new?  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
On Sat, 5 Jul 2025 12:58:10 -0700 Adrian Klaver wrote:

>On 7/5/25 11:24, pf@pfortin.com wrote:
>> On Sat, 5 Jul 2025 11:11:32 -0700 Adrian Klaver wrote:
>>   
>
>> Didn't try given:
>> $ df /mnt/db
>> Filesystem      Size  Used Avail Use% Mounted on
>> /dev/sdh1        17T   13T  3.0T  82% /mnt/db  
>
>You said you have ~70TB of free space, so where is the other  ~63TB?

I never said "free space" with ~70TB; that's the total space on about 8
drives :)
The biggest free space I have is 7.6TB which is less than the 8TB DB;
but thanks to the responses, I should be able to make this work...

Also, I appreciate the clarification re CREATE INDEX (Doh!) and --jobs

Best,
Pierre



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: pg_upgrade: can I use same binary for old & new?
Next
From: Soni M
Date:
Subject: Logical Replication 08P01 invalid memory alloc request size 1095736448