So the query is just the latest query and the time is the transaction time
since this query, i suppose ?
Thanks for your answer, i will try to make the transaction shorter as you
suggest.
On Tue, Jan 30, 2018 at 12:29 AM, Nikolay Samokhvalov wrote:
> On Mon, Jan 29, 2018 at 3:19 PM, Jan
The state is 'idle in transaction'.
On Tue, Jan 30, 2018 at 12:10 AM, Nikolay Samokhvalov wrote:
> On Mon, Jan 29, 2018 at 3:06 PM, Jan De Moerloose
> wrote:
> ...
>
>> SELECT pid, age(clock_timestamp(),query_start) as age, usename, query,
>> state
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.
