Re: our buffer replacement strategy is kind of lame - Mailing list pgsql-hackers

From Tom Lane
Subject Re: our buffer replacement strategy is kind of lame
Date
Msg-id 28052.1313341861@sss.pgh.pa.us
Whole thread Raw
In response to Re: our buffer replacement strategy is kind of lame  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: our buffer replacement strategy is kind of lame
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On Sat, Aug 13, 2011 at 11:14 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> I agree that something's missing.

> I'm quoting you completely out of context here, but yes, something is missing.

> We can't credibly do one test on usage count in shared buffers and
> then start talking about how buffer management is all wrong.

More generally: the originally presented facts suggest that there might
be value in improving the "buffer access strategy" code that keeps
particular operations from using all of shared_buffers.  It seems to me
to be a giant and unsubstantiated leap from that to the conclusion that
there's anything wrong with the clock sweep algorithm.  Moreover,
several of the proposed "fixes" amount to reversion to methods that
we already know are less good than the clock sweep, because we already
tried them years ago.  So I've been quite unimpressed with the quality
of discussion in this thread.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Connection Problem
Next
From: Tom Lane
Date:
Subject: VACUUM FULL versus unsafe order-of-operations in DDL commands