| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | pgsql-patches(at)postgresql(dot)org |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, "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:36:17 |
| Message-ID: | 200804032036.17604.xzilla@users.sourceforge.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
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)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-04-04 00:45:37 | Re: Expose checkpoint start/finish times into SQL. |
| Previous Message | Tom Lane | 2008-04-04 00:29:18 | Re: Expose checkpoint start/finish times into SQL. |