Re: should we set hint bits without dirtying the page?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: should we set hint bits without dirtying the page?
Date: 2010-12-03 02:54:01
Message-ID: 12011.1291344841@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I then got to wondering whether we should even go a step further, and
> simply decree that a page with only hint bit updates is not dirty and
> won't be written, period.

This sort of thing has been discussed before. It seems fairly clear to
me that any of these variations represents a performance tradeoff: some
cases will get better and some will get worse. I think we are not going
to get far unless we can agree on a set of benchmark cases that we'll
use to decide whether the tradeoff is a win or not. How can we arrive
at that?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2010-12-03 03:03:33 Re: WIP patch for parallel pg_dump
Previous Message Tom Lane 2010-12-03 02:41:53 Re: WIP patch for parallel pg_dump