shared memory size during upgrade pgsql with partitions - Mailing list pgsql-performance

From Piotr Włodarczyk
Subject shared memory size during upgrade pgsql with partitions
Date
Msg-id 86a9cb749c7749c2aeca5e1ebb212598@EX13MBX02.gb.ad.corp
Whole thread Raw
Responses Re: shared memory size during upgrade pgsql with partitions(max_locks_per_transaction)  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-performance
Hello,

Currently we're working on PSQL 11.5 and we're trying upgrade to 12.1.

During that we have a problem:

command: "/usr/pgsql-12/bin/pg_dump" --host /cluster/postgresql --port 50432
--username postgres --schema-only --quote-all-identifiers --binary-upgrade
--format=custom  --file="pg_upgrade_dump_281535902.custom" 'dbname=sprint'
>> "pg_upgrade_dump_281535902.log" 2>&1
pg_dump: error: query failed: ERROR:  out of shared memory
HINT:  You might need to increase max_locks_per_transaction.
pg_dump: error: query was: LOCK TABLE
"some_schemaa"."table_part_80000000_2018q3" IN ACCESS SHARE MODE

On current instance we have about one thousand of partitions, partitioned in
two levels: first by id_product, and second level by quarter of the year, as
you can see on above log.

How have we to calculate shared memory, and (eventually
max_locks_per_transaction) to be fit to the limits during upgrade?

Attachment

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: weird long time query
Next
From: Kaijiang Chen
Date:
Subject: Re: weird long time query