On Tue, May 22, 2012 at 12:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> With respect to the control logic for the background writer, one idea
>> I had was to get rid of the idea that the background writer's job is
>> to write in advance of the strategy point. Instead, every time the
>> clock sweep passes over a dirty buffer that is otherwise evictable, we
>> add it to a queue of things that the bgwriter should clean. Those
>> buffers, once cleaned, go on the free list. Maybe some variant of
>> that could work with your idea.
>
> Both ends of that imply centralized data structures that could become
> contention bottlenecks, so it doesn't sound tremendously appealing to
> me. Maybe it can work as long as nobody has to lock the lists for long,
> but I'd rather think of approaches with no central point of contention.
If we're going to throw our current algorithm over wholesale, I'd
rather use some approach that has been demonstrated to work well in
other systems. Buffer eviction is a problem that's been around since
the 1970s, and our algorithm is just about that old. I realize that
there are (legitimate) concerns about what might be patented, but
hopefully that doesn't mean we're not allowed to consult the
literature in any way. If that were the case, we wouldn't have SSI.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company