Re: Design notes for BufMgrLock rewrite - Mailing list pgsql-hackers

From Sailesh Krishnamurthy
Subject Re: Design notes for BufMgrLock rewrite
Date
Msg-id mjqhdkfil7h.fsf@drones.CS.Berkeley.EDU
Whole thread Raw
In response to Design notes for BufMgrLock rewrite  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
   Tom> and changing the buf_table hash table.  The only common   Tom> operation that needs exclusive lock is reading
ina page that   Tom> was not in shared buffers already, which will require at   Tom> least a kernel call and usually a
waitfor I/O, so it will be   Tom> slow anyway.
 

Why not a separate lock per bucket chain in the hash table in addition
to the system-wide LWLock ? It's not so much that such an operation will be
slow anyway but that such a slow operation will unnecessarily block
other operations.

-- 
Pip-pip
Sailesh
http://www.cs.berkeley.edu/~sailesh




pgsql-hackers by date:

Previous
From: "John Hansen"
Date:
Subject: Schema name of function
Next
From: Richard Huxton
Date:
Subject: Re: Dealing with network-dead clients