| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Theo Schlossnagle <jesus(at)omniti(dot)com> |
| Subject: | Re: Expose checkpoint start/finish times into SQL. |
| Date: | 2008-04-04 00:45:37 |
| Message-ID: | 47F57A31.6000508@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Robert Treat wrote:
> On Thursday 03 April 2008 19:08, Andrew Dunstan wrote:
>
>> Joshua D. Drake wrote:
>>
>>>> Theo Schlossnagle wrote:
>>>>
>>>>> First whack at exposing the start and finish checkpoint times into
>>>>> SQL.
>>>>>
>>>> Why is that useful?
>>>>
>>> For knowing how long checkpoints are taking. If they are taking too
>>> long you may need to adjust your bgwriter settings, and it is a
>>> serious drag to parse postgresql logs for this info.
>>>
>> Even if this were true, surely the answer is to improve the logging.
>>
>>
>
> Exposing everything into the log files isn't always sufficient (says the guy
> who maintains a remote admin tool)
>
It should be now that you can have machine readable logs (says the guy
who literally spent weeks making that happen) ;-)
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-04-04 01:14:57 | Re: Expose checkpoint start/finish times into SQL. |
| Previous Message | Robert Treat | 2008-04-04 00:36:17 | Re: Expose checkpoint start/finish times into SQL. |