Re: limiting hint bit I/O - Mailing list pgsql-hackers

From Robert Haas
Subject Re: limiting hint bit I/O
Date
Msg-id AANLkTi=ZzST4ecpDVu=DX1k8waf873X6XAXtJtGc++eb@mail.gmail.com
Whole thread Raw
In response to Re: limiting hint bit I/O  (Bruce Momjian <bruce@momjian.us>)
Responses Re: limiting hint bit I/O  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Sat, Feb 5, 2011 at 4:31 PM, Bruce Momjian <bruce@momjian.us> wrote:
> Uh, in this C comment:
>
> +        * or not we want to take the time to write it.  We allow up to 5% of
> +        * otherwise-not-dirty pages to be written due to hint bit changes,
>
> 5% of what?  5% of all buffers?  5% of all hint-bit-dirty ones?  Can you
> clarify this in the patch?

5% of buffers that are hint-bit-dirty but not otherwise dirty.  ISTM
that's exactly what the comment you just quoted says on its face, but
I'm open to some other wording you want to propose.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: limiting hint bit I/O
Next
From: Radosław Smogura
Date:
Subject: Varchar and binary protocol