Re: [GENERAL] Maximum number of exclusive locks

Jeff Janes writes: > On Tue, Sep 13, 2016 at 6:21 AM, Tom Lane wrote: >> Having said that, the amount of slop involved is only enough for a >> few hundred lock entries. Not sure how you're managing to get to >> nearly 2 extra entries. > The code

Re: [GENERAL] Maximum number of exclusive locks

On Tue, Sep 13, 2016 at 6:21 AM, Tom Lane wrote: > "Daniel Verite" writes: > > Nothing to complain about, but why would the above formula > > underestimate the number of object locks actually available > > to a transaction? Isn't it supposed to be a

Re: [GENERAL] Maximum number of exclusive locks

"Daniel Verite" writes: > Nothing to complain about, but why would the above formula > underestimate the number of object locks actually available > to a transaction? Isn't it supposed to be a hard cap for such > locks? No, it's a minimum not a maximum. There's

[GENERAL] Maximum number of exclusive locks

Hi, When deleting large objects, an exclusive lock is grabbed on each object individually. As a result, a transaction that does it en masse can encounter this error: ERROR: out of shared memory HINT: You might need to increase max_locks_per_transaction. I would expect the maximum number