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-06 03:38:59 |
Message-ID: | Pine.GSO.4.64.0703052234440.16130@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 21 Feb 2007, Robert Treat wrote:
> My impression of this is that DBA's would typically want to run this for a
> short period of time to get thier systems tuned and then it pretty much
> becomes chatter. Can you come up with an idea of what information DBA's need
> to know?
I am structing the log levels so that you can see all the events that are
likely sources for extreme latency by using log level DEBUG1. That level
isn't too chatty and I've decided I can leave the server there forever if
need by. I've actually come with a much better interface to the
background writer logging than the one I originally outlined, that I'll
have ready for feedback in a few more days. Now it dumps a nice summary
report every time it completes a scan, rather than logging lower-level
info.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-03-06 03:58:40 | Re: Bug: Buffer cache is not scan resistant |
Previous Message | Greg Smith | 2007-03-06 03:34:35 | Re: Log levels for checkpoint/bgwriter monitoring |