| From: | Aaron Held <aaron(at)MetroNY(dot)com> |
|---|---|
| To: | Roberto Mello <rmello(at)cc(dot)usu(dot)edu> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-sql(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [SQL] Monitoring a Query |
| Date: | 2002-09-23 14:31:18 |
| Message-ID: | 3D8F25B6.3090809@MetroNY.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
It looks like that just timestamps things in its connection pool, that
is what I do now.
What I would like is to know about queries that have not finished yet.
-Aaron
Roberto Mello wrote:
> On Sun, Sep 22, 2002 at 09:51:55PM -0400, Bruce Momjian wrote:
>
>>>Would it be a good idea to add the time that the current query began
>>>execution at to pg_stat_activity?
>>
>>What do people think about this? It seems like a good idea to me.
>
>
> OpenACS has a package called "Developer Support" that shows you (among
> other things) how long a query took to be executed. Very good to finding
> out slow-running queries that need to be optimized.
>
> -Roberto
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-23 14:37:27 | Re: Open Source Database article |
| Previous Message | Shridhar Daithankar | 2002-09-23 13:56:57 | Re: Postgresql Automatic vacuum |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-23 14:40:13 | Re: Problem on PG7.2.2 |
| Previous Message | Tom Lane | 2002-09-23 14:01:06 | Re: DROP COLUMN misbehaviour with multiple inheritance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-23 14:48:30 | Re: [SQL] Monitoring a Query |
| Previous Message | Thorbjörn Eriksson | 2002-09-23 14:28:41 | Re: Stripping white-space in SELECT statments |