Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Expose checkpoint start/finish times into SQL.


  • From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
  • To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
  • Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-patches(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, Theo Schlossnagle <jesus(at)omniti(dot)com>, "Joshua D. Drake" <jd(at)commandprompt(dot)com>
  • Subject: Re: Expose checkpoint start/finish times into SQL.
  • Date: Sat, 5 Apr 2008 14:00:15 -0400
  • Message-id: <20080405180015(dot)GC12256(at)alvh(dot)no-ip(dot)org>

Heikki Linnakangas wrote:
> Robert Treat wrote:

>> 2) Can be graphed over time (using rrdtool and others) for trending 
>> checkpoint activity
>
> Hmm. You'd need the historical data to do that properly. In particular,  
> if two checkpoints happen between the polling interval, you'd miss that.  

Yes, Munin and other tools collect the values over time to create the
graph.  It's not like "top" saves historical system load data either,
yet the collector is able to present you with a graph.

> log_checkpoints=on, in CSV output, seems like a better approach for that.

It's not, because the tool would have a much harder time trolling the
logs.  CSV does not really make it much easier -- the DBA is still
tasked with importing the thing after the current file is complete; and
you don't have an up-to-date picture either.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group