From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Practical maximum max_locks_per_transaction?
Date: Fri, 25 Nov 2022 17:45:42 -0600
Message-ID: <fa76c81e-723f-01ab-9155-927c549c79ec@gmail.com> (raw)
v9.6.24 (being retired next year)
https://www.postgresql.org/docs/9.6/runtime-config-locks.html
"The default, 64, has historically proven sufficient, but you might need to
raise this value if you have queries that touch many different tables in a
single transaction, e.g., query of a parent table with many children."
How "raised" is too raised? I just had to increase
max_locks_per_transaction from 640 to 1024 on an instance with many child
tables and against which is run many large reports. Another instance has
zero children, but had to increase the value to 1280 to prevent reports from
failing.
--
Angular momentum makes the world go 'round.
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: Practical maximum max_locks_per_transaction?
In-Reply-To: <fa76c81e-723f-01ab-9155-927c549c79ec@gmail.com>
References: <fa76c81e-723f-01ab-9155-927c549c79ec@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