| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Theo Schlossnagle <jesus(at)omniti(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Expose checkpoint start/finish times into SQL. |
| Date: | 2008-04-03 23:08:31 |
| Message-ID: | 47F5636F.200@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
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.
Has this feature been discussed on -hackers? I don't recall it (and my
memory has plenty of holes in it), but I'm sure that after attending my
talk last Sunday Theo hasn't sent in a patch for an undiscussed feature ;-)
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-04-03 23:30:20 | Re: psql \G command -- send query and output using extended format |
| Previous Message | Alvaro Herrera | 2008-04-03 22:48:19 | Re: psql \G command -- send query and output using extended format |