Skip site navigation (1) Skip section navigation (2)

Re: On the usefulness of hint bits

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Leonardo Francalanci <m_lists(at)yahoo(dot)it>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: On the usefulness of hint bits
Date: 2010-10-11 15:20:41
Message-ID: AANLkTik5adeLM+puT8BsSMPJK_knS0jEb193g2xmhyE7@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Oct 11, 2010 at 10:14 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Reduction of contention for pg_clog access, for one thing.  If you read
> the archives, you'll find that pg_clog access contention has been shown
> to be one cause of "context swap storms".

I wonder if we could improve this with some sort of process-local
cache - not to get rid of hint bits, just to reduce pg_clog
contention.  We might easily end up testing the same XID many times
during the same table scan.

Another idea that's been discussed before is to avoid writing out
pages when only the hit bints have changed.  Or perhaps to write them
out from the background writer only, but not from backends and not
when checkpointing - have a state BM_UNTIDY, which the background
writer cleaning scan will treat as dirty, but which can otherwise be
treated as "not dirty", so that if we start to run short of free
buffers we don't hold things up writing out the hint bit updates.

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

In response to

Responses

pgsql-hackers by date

Next:From: Dean RasheedDate: 2010-10-11 15:30:46
Subject: Re: wip: functions median and percentile
Previous:From: Leonardo FrancalanciDate: 2010-10-11 15:03:03
Subject: Re: On the usefulness of hint bits

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group