From: Jeff Ross <jross@openvistas.net>
To: pgsql-general@lists.postgresql.org
Subject: Re: 15 pg_upgrade with -j
Date: Tue, 23 May 2023 08:43:54 -0600
Message-ID: <79a10835-e830-51f0-bdc1-596807aa5b7a@openvistas.net> (raw)
In-Reply-To: <8b4034c6-ca1b-b0bb-e067-685235775395@aklaver.com>
References: <85a18793-627a-2a8b-1296-c965505694e6@openvistas.net>
<13b3d746-a980-22d9-c88b-e74451536a11@aklaver.com>
<5fdaee55-81df-4be8-73c9-8e496bd02368@openvistas.net>
<8b4034c6-ca1b-b0bb-e067-685235775395@aklaver.com>
On 5/22/23 5:43 PM, Adrian Klaver wrote:
>
>>>
>>> From docs:
>>>
>>> https://www.postgresql.org/docs/current/pgupgrade.html
>>>
>>> The --jobs option allows multiple CPU cores to be used for
>>> copying/linking of files and to dump and restore database schemas in
>>> parallel; a good place to start is the maximum of the number of CPU
>>> cores and tablespaces. This option can dramatically reduce the time
>>> to upgrade a multi-database server running on a multiprocessor machine.
>>>
>>> So is the 1400G mostly in one database in the cluster?
>>>
>>>>
>>>> The full commands we are using for pg_upgrade are pretty stock:
>
>> Yes, one big database with about 80 schemas and several other smaller
>> databases so -j should help, right?
>
>
> As I understand it no. That the parallelism is between databases not
> within a database. Further that 'database schemas' refers to schema as
> the overall database object definitions not the namespaces known as
> schemas in the database.
Thanks Adrian. That "restore database schemas in parallel" phrase seems
like it would be really easy to read like we did and expect it to work
with one database and multiple schemas.
Maybe it should be changed to "restore multiple databases in parallel"
instead?
Jeff
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: jross@openvistas.net
Subject: Re: 15 pg_upgrade with -j
In-Reply-To: <79a10835-e830-51f0-bdc1-596807aa5b7a@openvistas.net>
References: <85a18793-627a-2a8b-1296-c965505694e6@openvistas.net> <13b3d746-a980-22d9-c88b-e74451536a11@aklaver.com> <5fdaee55-81df-4be8-73c9-8e496bd02368@openvistas.net> <8b4034c6-ca1b-b0bb-e067-685235775395@aklaver.com> <79a10835-e830-51f0-bdc1-596807aa5b7a@openvistas.net>
* 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