From: Simon Riggs <simon@2ndquadrant.com>
To: Dan Gorman <dgorman@hi5.com>
Cc: mischa@ca.sophos.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Selects query stats?
Date: Tue, 23 May 2006 19:51:12 +0100
Message-ID: <1148410273.2755.179.camel@localhost.localdomain> (raw)
In-Reply-To: <127D68F6-7620-4A62-8D1A-9B475E7571CD@hi5.com>
References: <9C4E40CF-6C06-4297-AF32-A7EF2A3F3C0F@hi5.com>
<4473512E.7020805@ca.sophos.com>
<82252882-2A15-4823-A517-7AB3161889D1@hi5.com>
<4473553C.1010804@ca.sophos.com>
<127D68F6-7620-4A62-8D1A-9B475E7571CD@hi5.com>
On Tue, 2006-05-23 at 11:33 -0700, Dan Gorman wrote:
> In any other DB (oracle, mysql) I know how many queries (selects) per
> second the database is executing. How do I get this
> number out of postgres?
>
>
> I have a perl script that can test this, but no way the db tells me
> how fast it's going.
>
>
> (e.g. in oracle: select sum(executions) from v$sqlarea;)
The Oracle query you show doesn't do that either. It tells you how many
statements have been executed since startup, not per second.
The main problem with what you ask is it only seems to have value. If
the value dips for some reason, you have no way of knowing whether that
occurred because the arrival rate dropped off, there is a system problem
or whether statements just happened to access more data over that time
period. You can collect information that would allow you to understand
what is happening on your system and summarise that as you choose.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
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-performance@postgresql.org
Cc: simon@2ndquadrant.com, dgorman@hi5.com, mischa@ca.sophos.com
Subject: Re: Selects query stats?
In-Reply-To: <1148410273.2755.179.camel@localhost.localdomain>
* 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