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

From Bruce Momjian
Subject Re: Design notes for BufMgrLock rewrite
Date
Msg-id 200502132340.j1DNeGR19532@candle.pha.pa.us
Whole thread Raw
In response to Design notes for BufMgrLock rewrite  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Design notes for BufMgrLock rewrite  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Design notes for BufMgrLock rewrite  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Tom Lane wrote:
> I'm working on an experimental patch to break up the BufMgrLock along
> the lines we discussed a few days ago --- in particular, using a clock
> sweep algorithm instead of LRU lists for the buffer replacement strategy.
> I started by writing up some design notes, which are attached for
> review in case anyone has better ideas.
> 
> One thing I realized quickly is that there is no natural way in a clock
> algorithm to discourage VACUUM from blowing out the cache.  I came up
> with a slightly ugly idea that's described below.  Can anyone do better?

Uh, is the clock algorithm also sequential-scan proof?  Is that
something that needs to be done too?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Design notes for BufMgrLock rewrite
Next
From: Bruce Momjian
Date:
Subject: Re: Goals for 8.1