Manfred Spraul wrote:
> The scary part from the system perspective are the 35 million context
> switches that were generated by the BufMgrLock and the LockMgrLock. I
> remember there were patches that tried other algorithms instead of the
> simple LRU for the buffer manager. Has anyone tried to
Tom Lane wrote:
Is there an easy way find out which LWLock is contended?
Not from oprofile output, as far as I can think. I've suspected for
some time that the BufMgrLock is a major bottleneck, but have no proof.
Mark ran a DBT-2 testrun with the attached statistics patch applied: It
col
