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

From: Pierre Fortin <pf(at)pfortin(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade: can I use same binary for old & new?
Date: 2025-07-05 21:11:55
Message-ID: 20250705171155.1c857f82@pfortin.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, 5 Jul 2025 12:58:10 -0700 Adrian Klaver wrote:

>On 7/5/25 11:24, pf(at)pfortin(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Soni M 2025-07-06 09:40:55 Logical Replication 08P01 invalid memory alloc request size 1095736448
Previous Message Adrian Klaver 2025-07-05 20:23:18 Re: pg_upgrade: can I use same binary for old & new?