Re: Log levels for checkpoint/bgwriter monitoring

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Log levels for checkpoint/bgwriter monitoring
Date: 2007-03-14 04:13:04
Message-ID: Pine.GSO.4.64.0703132350420.26349@westnet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 12 Mar 2007, Tom Lane wrote:

> It might also be interesting to know exactly how many buffers were
> pinned at the time the scan passed over them. In theory it should be a
> small fraction, but maybe it isn't ...

It is; the theory holds for all the tests I tried today. The actual
pinned buffers were so few (typically a fraction of the clients) that I
reverted to just lumping them in with the recently used ones. To better
reflect the vast majority of what it's interacting with, in my patch I
renamed the SyncOneBuffer "skip_pinned" to "skip_recently_used". It seems
natural that something currently pinned would also be considered recently
used, the current naming I didn't find so obvious.

I'm also now collecting clean vs. dirty usage histogram counts as well
since you suggested it. Nothing exciting to report there so far, may note
something interesting after I collect more data.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paesold 2007-03-14 07:01:53 Re: Bug in UTF8-Validation Code?
Previous Message Edward Stanley 2007-03-13 23:07:45 Re: My honours project - databases using dynamically attached entity-properties