Re: Thinking about breaking up the BufMgrLock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Thinking about breaking up the BufMgrLock
Date: 2005-02-07 04:17:12
Message-ID: 18903.1107749832@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark <gsstark(at)mit(dot)edu> writes:
> I recall the clock sweep having
> been recommended in class as having most of the best properties of LRU with
> very low cost in the critical path.

Right. The "pending move to front" idea that I suggested is basically a
variant of a clock algorithm: it takes two trips through the LRU list
before a page falls off and becomes eligible for replacement. (It's
even closer to the "second chance" clock algorithm.)

The $64 question with any of these things is how much performance at the
cache-management level are we willing to give up in order to gain
low-level efficiency? We probably don't want to go very far in that
direction. But maybe a clock scan will be a good compromise.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Premsun Choltanwanich 2005-02-07 04:40:41 How can I use large object on PostgreSQL Linux Version?
Previous Message Greg Stark 2005-02-07 03:53:38 Re: Thinking about breaking up the BufMgrLock