From: Neil Conway <neilc@samurai.com>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Jim C. Nasby <decibel@decibel.org>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Performance monitoring
Date: Sun, 13 May 2007 00:41:24 -0400
Message-ID: <1179031284.2830.19.camel@goldbach> (raw)
In-Reply-To: <464630EA.5000701@commandprompt.com>
References: <Pine.GSO.4.64.0704010051050.14920@westnet.com>
<200704030814.33999.peter_e@gmx.net>
<Pine.GSO.4.64.0704030927180.5732@westnet.com>
<46443F02.6060300@enterprisedb.com>
<Pine.GSO.4.64.0705111009080.18685@westnet.com>
<46448DC8.4050102@enterprisedb.com>
<20070512211948.GA58786@nasby.net>
<464630EA.5000701@commandprompt.com>
On Sat, 2007-12-05 at 14:26 -0700, Joshua D. Drake wrote:
> Either way, we are taking the hit, it is just a matter of where. IMO it
> would be better to have the information in the database where it makes
> sense, than pushing out to a log
If performance monitoring information is provided as a database object,
what would the right interface be? IMHO the problem with cleanly
presenting monitoring information within a normal database system is
that this sort of data is fundamentally dynamic and continuous: to
determine how the performance of the system changes over time, you need
to repeatedly rescan the table/view/SRF and recompute your analysis
essentially from scratch. Trying to get even simple information like
"queries per second" from pg_stat_activity is an example of how this can
be painful.
<plug>
BTW, if the system included the concept of a continuous data *stream* as
a kind of database object, this problem would be much more tractable :)
In fact, there is some code in a version of TelegraphCQ that exposes
various information about the runtime state of the system as a set of
system-defined data streams -- like any other stream, users could then
use those streams in arbitrary queries.
</plug>
-Neil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: neilc@samurai.com, jd@commandprompt.com, decibel@decibel.org, heikki@enterprisedb.com, gsmith@gregsmith.com
Subject: Re: Performance monitoring
In-Reply-To: <1179031284.2830.19.camel@goldbach>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox