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, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
