Re: 15 pg_upgrade with -j

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Ross <jross(at)openvistas(dot)net>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: 15 pg_upgrade with -j
Date: 2023-05-22 23:42:14
Message-ID: 774330.1684798934@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeff Ross <jross(at)openvistas(dot)net> writes:
> On 5/22/23 5:24 PM, Adrian Klaver wrote:
>> So is the 1400G mostly in one database in the cluster?

> Yes, one big database with about 80 schemas and several other smaller
> databases so -j should help, right?

AFAICT from a quick look at the code, you won't get any meaningful
parallelism unless you have several large DBs and/or several large
tablespaces. It looks like the assumption was that issuing link()
requests in parallel wouldn't help much but just swamp your disk
if they're all on the same filesystem. Maybe that could use
rethinking, not sure.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2023-05-22 23:43:38 Re: 15 pg_upgrade with -j
Previous Message Jeff Ross 2023-05-22 23:29:39 Re: 15 pg_upgrade with -j