I see this in the CVS commits for 8.2.  Did we determine the proper
number of lock partitions?  Should it be based on the number of buffers
or concurrent sessions allowed?

 Divide the lock manager's shared state into 'partitions', so as to
 reduce contention for the former single LockMgrLock.  Per my recent
 proposal.  I set it up for 16 partitions, but on a pgbench test this
 gives only a marginal further improvement over 4 partitions --- we need
 to test more scenarios to choose the number of partitions.

  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to