From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general <pgsql-general@postgresql.org>
Subject: pg_upgrade and schema complexity...
Date: Fri, 2 Jun 2023 19:44:07 -0500
Message-ID: <6185dd27-b3d3-b594-33fc-58345df79a13@gmail.com> (raw)
Ran into this when upgrading from 13.11 to 15.3...
The pg_restore phase failed with "ERROR: out of shared memory", and
recommended that I increase max_locks_per_transaction. Doing so let the
process run to completion.
It took 12.5 minutes to upgrade a 13GB instance. Soon after, I upgraded a
78GB cluster, and it only took 3.1 minutes.
(Both are VMs (same number of CPUs and RAM) connected to the same SAN.)
A "pg_dump --schema-only" of the two systems shows that the small-but-slow
schema is 5.9M lines.
Is this to be expected of such a huge schema?
--
Born in Arizona, moved to Babylonia.
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: pg_upgrade and schema complexity...
In-Reply-To: <6185dd27-b3d3-b594-33fc-58345df79a13@gmail.com>
References: <6185dd27-b3d3-b594-33fc-58345df79a13@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