From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Script and tool to monitoring sessions |
Date: | 2015-09-25 09:04:34 |
Message-ID: | mu32n2$93t$1@ger.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
abdujaparov schrieb am 25.09.2015 um 10:38:
> Hi,
> I am checking
>
> SELECT * FROM pg_stat_activity;
>
> during the ingestion process:
>
> 19028;"smapdb";1151;19029;"smap";"";"172.25.10.42";"";62921;"2015-09-25
> 10:30:31.523041+02";"2015-09-25 10:30:38.013215+02";"2015-09-25
> 10:34:17.075262+02";"2015-09-25 10:34:17.075295+02";f;"idle in
> transaction";;2765;"select nextval ('public.l3smap_partition_id_seq')"
>
> This is the ingestion process that is running. I think that all the time is
> spent on the sequence is it correct?
>
The column "query" only reflects the _current_ statement if state = 'active' at the same time.
In the above result, the session is not doing anything ("idle") and the *last* statement it executed, was the "select nexval()".
The session is in "idle in transaction" which means that it started a transaction but has not yet committed it.
From | Date | Subject | |
---|---|---|---|
Next Message | abdujaparov | 2015-09-25 10:25:39 | Re: Script and tool to monitoring sessions |
Previous Message | Jayadevan M | 2015-09-25 08:58:32 | Re: Script and tool to monitoring sessions |