Practical maximum max_locks_per_transaction?

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Practical maximum max_locks_per_transaction?
Date: 2022-11-25 23:45:42
Message-ID: fa76c81e-723f-01ab-9155-927c549c79ec@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2022-11-25 23:56:17 Re: Practical maximum max_locks_per_transaction?
Previous Message Zheng Li 2022-11-25 22:23:09 Re: Support logical replication of DDLs