On 10/16/23 14:31, Craig McIlwee wrote:
That's what we've already done for the short term solution. It is
somewhat in conflict with your statement regarding the number of lockable
objects not holding still for long, though. As time goes on and our
scheduled jobs automatically create new month
On Mon, Oct 16, 2023 at 2:32 PM Tom Lane wrote:
> Craig McIlwee writes:
> > Most discussions regarding the lock table say that the size of the lock
> > table determines how many locks can be held. The documentation for
> > max_locks_per_transaction [3] reads slightly different though, and in
>
Craig McIlwee writes:
> Most discussions regarding the lock table say that the size of the lock
> table determines how many locks can be held. The documentation for
> max_locks_per_transaction [3] reads slightly different though, and in
> particular this phrases stands out to me:
>> no more than
We're using PostgreSQL 13.10, installed on CentOS 7 from PGDG RPMs.
Recently we've run into "out of shared memory" issues with a hint at
increasing max_locks_per_transaction. The problem is well described in the
PostgreSQL documentation and various blog posts found around the internet,
and the so
