| From: | Jan De Moerloose <jan(at)sensolus(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Meaning of query age in pg_stat_activity |
| Date: | 2018-01-29 23:06:36 |
| Message-ID: | CAF06xsTLGXpYKfP3RtWW_-VP0RE28+V6mv8fJHXB6y1xFzsgoA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
I'm using the following to detect long running queries in a webapp that is
high on cpu:
SELECT pid, age(clock_timestamp(),query_start) as age, usename, query,
state from pg_stat_activity order by age;
When the cpu is 100% and the app slowing down, i can see that some queries
have a long age.
Running the same queries in psql is very fast, however. The db itself is
low on cpu.
Is the age value as i calculate it representing the time spent by the
database to execute the query or does it also include the time to read the
result ? In other words, if the client is starving on cpu, will i see
higher values of age ?
Regards,
Jan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Samokhvalov | 2018-01-29 23:10:37 | Re: Meaning of query age in pg_stat_activity |
| Previous Message | Tatsuo Ishii | 2018-01-29 22:46:30 | Re: pgpool Connections Distributions Among Nodes |