Practical maximum max_locks_per_transaction? - Mailing list pgsql-general

From Ron
Subject Practical maximum max_locks_per_transaction?
Date
Msg-id fa76c81e-723f-01ab-9155-927c549c79ec@gmail.com
Whole thread Raw
Responses Re: Practical maximum max_locks_per_transaction?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.

pgsql-general by date:

Previous
From: Andrus
Date:
Subject: How to create hot standby of Postgres 12/Debian 10.3 in Windows 11
Next
From: Tom Lane
Date:
Subject: Re: Practical maximum max_locks_per_transaction?