From: | abdujaparov <afmulone(at)gmail(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Script and tool to monitoring sessions |
Date: | 2015-09-25 10:25:39 |
Message-ID: | 1443176739129-5867352.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hi,
I am trying to understand.
From hibernate we see that there is a begin transaction and there is only
one final commit.
From Server status of pgAdmin I see that that the processes c
10505 smapdb smap 172.25.10.102:51835 2015-09-25 12:16:52+02 2015-09-25
12:16:56+02
execute select nextval ('public.L3SmAp_id_seq')
and status changes continuously from
'idle in transaction' and 'active'
After that I see two lock from pid 10505:
ExclusiveLock
AccessShareLock
both these locks are related to select nextval ('public.L3SmAp_id_seq').
Angelo
--
View this message in context: http://postgresql.nabble.com/Script-and-tool-to-monitoring-sessions-tp5867117p5867352.html
Sent from the PostgreSQL - novice mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | KK | 2015-09-29 06:01:51 | Tainted kernel possible caused by postgresql |
Previous Message | Thomas Kellerer | 2015-09-25 09:04:34 | Re: Script and tool to monitoring sessions |