From: Piotr Włodarczyk <piotr.wlodarczyk@gnb.pl>
To: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: shared memory size during upgrade pgsql with partitions
Date: Tue, 17 Dec 2019 20:03:41 +0000
Message-ID: <86a9cb749c7749c2aeca5e1ebb212598@EX13MBX02.gb.ad.corp> (raw)
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?
Attachments:
[application/pkcs7-signature] smime.p7s (5.4K, ../86a9cb749c7749c2aeca5e1ebb212598@EX13MBX02.gb.ad.corp/2-smime.p7s)
download
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: piotr.wlodarczyk@gnb.pl, pgsql-performance@lists.postgresql.org
Subject: Re: shared memory size during upgrade pgsql with partitions
In-Reply-To: <86a9cb749c7749c2aeca5e1ebb212598@EX13MBX02.gb.ad.corp>
* 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