From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade and schema complexity... |
Date: | 2023-06-03 00:58:06 |
Message-ID: | 9648047c-1895-2480-c1af-164672a3188e@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/2/23 17:44, Ron wrote:
> 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.
Where/how did you measure those sizes?
>
> (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.
Anything special you are doing in this cluster to create all those lines?
What is the line count for the other instance?
>
> Is this to be expected of such a huge schema?
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-06-03 01:06:15 | Re: pg_upgrade and schema complexity... |
Previous Message | Ron | 2023-06-03 00:44:07 | pg_upgrade and schema complexity... |