Re: Practical maximum max_locks_per_transaction?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Practical maximum max_locks_per_transaction?
Date: 2022-11-25 23:56:17
Message-ID: 25925.1669420577@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron <ronljohnsonjr(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2022-11-26 07:33:15 Re: Practical maximum max_locks_per_transaction?
Previous Message Ron 2022-11-25 23:45:42 Practical maximum max_locks_per_transaction?