Hi James,
Take a look here, in the links you will find many info and real examples
for LockManager issues.
https://ardentperf.com/2024/03/03/postgres-indexes-partitioning-and-lwlocklockmanager-scalability/
Luiz
On Tue, Apr 9, 2024 at 4:08 AM James Pang wrote:
>we found sometimes , with ma
I need to rectify myself: LWLock is not a spinlock (anymore).
The documentation in lwlock.c makes it clear that it used to be spinlock, but
now is a counter modified by atomic instructions.
Oh, I forgot to answer:
> you mean too many concurrent sessions trying to acquire lock on same relation
James,
A lock can be obtained in the parse, plan and execute step, depending on cache,
state and type of object.
A LWLock is a spinlock, a low level access mechanism that is supposed to be
extremely quickly. It is used to serialise access to elementary structures
mostly for changes.
A Lock is
you mean too many concurrent sessions trying to acquire lock on same
relation , then waiting on "LockManager" LWlock,right? this contention
occurred on parsing ,planning, or execute step ?
Thanks,
James
Laurenz Albe 於 2024年4月9日週二 下午12:31寫道：
> On Tue, 2024-04-09 at 11:07 +0800, James Pang wro
