From: | Jan De Moerloose <jan(at)sensolus(dot)com> |
---|---|
To: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Meaning of query age in pg_stat_activity |
Date: | 2018-01-29 23:45:45 |
Message-ID: | CAF06xsSczrCnPxoAmhOxbU4QN5K-iLtbmF_Ew=zB0S4Z_gg-zA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 <samokhvalov(at)gmail(dot)com
> wrote:
> On Mon, Jan 29, 2018 at 3:19 PM, Jan De Moerloose <jan(at)sensolus(dot)com>
> wrote:
>
>> The state is 'idle in transaction'.
>>
>
> So you have long-running *transactions*, not queries. This is not good for
> an OLTP system, because some transaction can wait of others, which are
> "idle in transaction" but do nothing at the moment. Think how you can make
> them shorter, commit faster.
>
> Also, if your server version is 9.6+ consider setting
> idle_in_transaction_session_timeout to some low value:
> https://www.postgresql.org/docs/current/static/runtime-
> config-client.html#GUC-IDLE-IN-TRANSACTION-SESSION-TIMEOUT
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | PT | 2018-01-29 23:55:16 | Re: best way to storing logs |
Previous Message | Nikolay Samokhvalov | 2018-01-29 23:29:49 | Re: Meaning of query age in pg_stat_activity |