pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: 15 pg_upgrade with -j
Date: Mon, 22 May 2023 21:10:48 -0500
Message-ID: <a3b25cac-1f54-99c8-1bf4-91ade7d94e4d@gmail.com> (raw)
In-Reply-To: <774330.1684798934@sss.pgh.pa.us>
References: <85a18793-627a-2a8b-1296-c965505694e6@openvistas.net>
	<13b3d746-a980-22d9-c88b-e74451536a11@aklaver.com>
	<5fdaee55-81df-4be8-73c9-8e496bd02368@openvistas.net>
	<774330.1684798934@sss.pgh.pa.us>

On 5/22/23 18:42, Tom Lane wrote:
> Jeff Ross <jross@openvistas.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.

Hmm.  I'm glad I'm reading this now.

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

It does need rethinking in the era of VMs and SANs. /var/lib/pgsql/15 is 
going to be on a different LUN from /var/lib/pgsql/9.6 just like 
/var/lib/pgsql/backups is on a different LUN.

-- 
Born in Arizona, moved to Babylonia.





view thread (14+ messages)  latest in thread

Message-ID: <a3b25cac-1f54-99c8-1bf4-91ade7d94e4d@gmail.com>
Permalink:  ../a3b25cac-1f54-99c8-1bf4-91ade7d94e4d@gmail.com/
Also on:    postgresql.org/message-id/a3b25cac-1f54-99c8-1bf4-91ade7d94e4d@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: 15 pg_upgrade with -j
  In-Reply-To: <a3b25cac-1f54-99c8-1bf4-91ade7d94e4d@gmail.com>
  References: <85a18793-627a-2a8b-1296-c965505694e6@openvistas.net> <13b3d746-a980-22d9-c88b-e74451536a11@aklaver.com> <5fdaee55-81df-4be8-73c9-8e496bd02368@openvistas.net> <774330.1684798934@sss.pgh.pa.us> <a3b25cac-1f54-99c8-1bf4-91ade7d94e4d@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox