Re: 2nd Level Buffer Cache - Mailing list pgsql-hackers

From Robert Haas
Subject Re: 2nd Level Buffer Cache
Date
Msg-id AANLkTiktwL=AUCucv6=VqVzfx+AP8hxf8g-eYoa1NMP1@mail.gmail.com
Whole thread Raw
In response to Re: 2nd Level Buffer Cache  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 2nd Level Buffer Cache
List pgsql-hackers
On Wed, Mar 23, 2011 at 6:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> It looks like the only way anything can ever get put on the free list
>> right now is if a relation or database is dropped.  That doesn't seem
>> too good.
>
> Why not?  AIUI the free list is only for buffers that are totally dead,
> ie contain no info that's possibly of interest to anybody.  It is *not*
> meant to substitute for running the clock sweep when you have to discard
> a live buffer.

It seems at least plausible that buffer allocation could be
significantly faster if it need only pop the head of a list, rather
than scanning until it finds a suitable candidate.  Moving as much
buffer allocation work as possible into the background seems like it
ought to be useful.

Granted, I've made no attempt to code or test this.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Radosław Smogura
Date:
Subject: Re: 2nd Level Buffer Cache
Next
From: Stephen Frost
Date:
Subject: Pre-set Hint bits/VACUUM FREEZE on data load..?