Re: Log levels for checkpoint/bgwriter monitoring - Mailing list pgsql-hackers

From Greg Smith
Subject Re: Log levels for checkpoint/bgwriter monitoring
Date
Msg-id Pine.GSO.4.64.0703052224480.16130@westnet.com
Whole thread Raw
In response to Re: Log levels for checkpoint/bgwriter monitoring  ("Jim C. Nasby" <jim@nasby.net>)
Responses Re: Log levels for checkpoint/bgwriter monitoring  (Jim Nasby <decibel@decibel.org>)
List pgsql-hackers
On Thu, 22 Feb 2007, Jim C. Nasby wrote:

> It would also be extremely useful to make checkpoint stats visible 
> somewhere in the database (presumably via the existing stats 
> mechanism)... I'm thinking just tracking how many pages had to be 
> flushed during a checkpoint would be a good start.

I'm in the middle of testing an updated version of the patch, once I nail 
down exactly what needs to be logged I'd planned to open a discussion on 
which of those things would be best served by pg_stats instead of a log.

I decided specifically to aim for the logs instead for the checkpoint data 
because if you're in a situation where are inserting fast enough that the 
checkpoints are spaced closely together, you'd end up having to poll 
pg_stats all the time for make sure you catch them all, which becomes even 
less efficient than just logging the data.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES]
Next
From: Greg Smith
Date:
Subject: Re: Log levels for checkpoint/bgwriter monitoring