Re: Idle Sessions inTransaction with RELEASE_EXEC_SVP queries and locks

From: Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>
To: chris(dot)jurado(at)primesoft(dot)ph
Cc: PostgreSQL General Discussion Forum <pgsql-general(at)postgresql(dot)org>
Subject: Re: Idle Sessions inTransaction with RELEASE_EXEC_SVP queries and locks
Date: 2014-12-10 03:05:44
Message-ID: CADp-Sm4XzUmam8AdyBPc2m5=6zjSDrozKpTqageP8_5tCCFbuQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10 Dec 2014 08:52, <chris(dot)jurado(at)primesoft(dot)ph> wrote:
>
> ​I am having a problem with having idle sessions in transactions. In
pgAdmin Server Status, it is showing "RELEASE_EXEC_SVP_XXXXXX" (XXXXXX data
are varied) as its query and it's locks also contain a lot of these
"RELEASE_EXEC_SVP_XXXXXX" entries. What do these mean? These commonly cause
lock blocking problems because these sessions sometimes lock other rows but
the session status is always "Idle in transaction". I do not know why there
are sessions like these. I have reviewed our system and do not see any
possibility of transactions getting started that are not rollbacked or
committed and just stay idle so this must be something internal to
postgresql.
>
> Version of PostgreSQL is 9.2.8 running on Windows using psqlodbc driver
9.0.3.210.

What is the application platform? I know there are some APIs/packages in
languages viz python which would start an implicit transaction even when
you fire a select statement. What is the kind of lock and what is their
granted status?

What is the isolation level that you use in application?

Regards
Sameer Kumar
Ashnik Pte Ltd, Singapore

In response to

Browse pgsql-general by date

  From Date Subject
Next Message M Tarkeshwar Rao 2014-12-10 06:20:39 Re: FW: getting error while running sql on mm_activealrm table
Previous Message Peter Geoghegan 2014-12-10 02:06:13 Re: Weird CPU utilization patterns with Postgres