| From: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
|---|---|
| To: | Jan De Moerloose <jan(at)sensolus(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Meaning of query age in pg_stat_activity |
| Date: | 2018-01-30 06:04:14 |
| Message-ID: | CANNMO+JojuMWc7wCjvi_QRHfacfJtcZxdu8b=ohpEyZM8Uq6Tg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jan 29, 2018 at 9:52 PM, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>
wrote:
>
>
> On Mon, Jan 29, 2018 at 3:45 PM, Jan De Moerloose <jan(at)sensolus(dot)com>
> wrote:
>
>> 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.
>>
>
> Yep. This is a very common confusion, however it usually happens regarding
> records with "state" = 'idle'
> – notice that they also have something in "query" column while they are
> actually doing nothing.
>
One correction:
"the time is the transaction time since this query" is not an accurate
statement.
You mentioned query_start – it reflects the last query's starting time, not
transaction's.
There are other timestamps:
backend_start, xact_start, and state_change.
All of them are useful in different contexts.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2018-01-30 07:48:22 | session_replication_role meaning? |
| Previous Message | Nikolay Samokhvalov | 2018-01-30 05:52:00 | Re: Meaning of query age in pg_stat_activity |