Re: Process local hint bit cache - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Process local hint bit cache
Date
Msg-id AANLkTi=D9YmB1XRU6R96pvWtkFukz2Wd7eH3KC_g625s@mail.gmail.com
Whole thread Raw
In response to Re: Process local hint bit cache  (Greg Stark <gsstark@mit.edu>)
Responses Re: Process local hint bit cache
List pgsql-hackers
On Wed, Mar 30, 2011 at 10:40 AM, Greg Stark <gsstark@mit.edu> wrote:
> But one way or another the hint bits have to get set sometime. The
> sooner that happens the less clog i/o has to happen in the meantime.

I talked about this with Merlin a bit yesterday.  I think that his
thought is that most transactions will access a small enough number of
distinct CLOG pages, and the cache accesses might be fast enough, that
we really wouldn't need to get the hint bits set, or at least that
vacuum/freeze time would be soon enough.  I'm not sure if that's
actually true, though - I think the overhead of the cache might be
higher than he's imagining.  However, there's a sure-fire way to find
out... code it up and see how it plays.

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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Problem with pg_upgrade?
Next
From: Merlin Moncure
Date:
Subject: Re: Process local hint bit cache