Re: pg_check_queries.pl: an ineffective way to check for slow queries?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-admin(at)postgresql(dot)org>, "Mark Stosberg" <mark(at)summersault(dot)com>
Subject: Re: pg_check_queries.pl: an ineffective way to check for slow queries?
Date: 2009-07-03 18:35:43
Message-ID: 4A4E092F0200002500028360@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Mark Stosberg <mark(at)summersault(dot)com> wrote:

> What luck have others of you had with devising a way to monitor if
> your PostgreSQL server is "slow" ?

For web apps we submit HTTP requests to our renderers periodically,
and monitor the response time. Of course, this tests the whole stack,
but that's a good thing from our perspective.

For other software, we log queries which take more than two seconds,
and investigate performance complaints from our end users. There is
too much variation in run times, partly based on selection criteria
entered by users at run time, for us to want to automatically alert
based on run time.

Ultimately, for us, the only performance metric which really matters
for much of our software is user satisfaction with response time.

-Kevin

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Benjamin Krajmalnik 2009-07-03 21:23:28 Statistical tracking issue
Previous Message Mark Stosberg 2009-07-03 16:54:43 pg_check_queries.pl: an ineffective way to check for slow queries?