Re: Practical maximum max_locks_per_transaction? - Mailing list pgsql-general

From Tom Lane
Subject Re: Practical maximum max_locks_per_transaction?
Date
Msg-id 25925.1669420577@sss.pgh.pa.us
Whole thread Raw
In response to Practical maximum max_locks_per_transaction?  (Ron <ronljohnsonjr@gmail.com>)
Responses Re: Practical maximum max_locks_per_transaction?
List pgsql-general
Ron <ronljohnsonjr@gmail.com> writes:
> 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.

max_locks_per_transaction in isolation means nothing.  What counts
is the product max_locks_per_transaction * max_connections, which is
(more or less) the number of slots allocated in the shared lock table.

Having said that, you can probably make it as big as you want
on any reasonably modern machine.  I wouldn't blink at a few
million locktable entries, at least not on 64-bit hardware.

            regards, tom lane



pgsql-general by date:

Previous
From: Ron
Date:
Subject: Practical maximum max_locks_per_transaction?
Next
From: Ron
Date:
Subject: Re: Practical maximum max_locks_per_transaction?