Skip site navigation (1) Skip section navigation (2)

Re: Long running transaction in pg_activity_log

From: Tobias Brox <tobias(at)nordicbet(dot)com>
To: Sachchida Ojha <sojha(at)secure-elements(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Long running transaction in pg_activity_log
Date: 2007-08-22 21:08:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
[Sachchida Ojha - Wed at 04:40:09PM -0400]
> I see some long running transaction in my pg_activity_log table. My app
> becomes almost unusable. My question is 
> How can I query the database to see what sql these transactions are
> running. 

"<IDLE> in transaction" means that no sql query is running at the

Most probably it's a problem with the application, it starts a
transaction, but does not close it (through a commit or rollback).  This
is very harmful for the performance, as the hours, days and weeks pass
by any database supporting transactions will get problems.

Restarting the application and vacuuming is a one-time-shot which should
solve the problem for a short while.  For a permanent fix, the
application needs to be fixed, or you'll have to ensure that the
autocommit feature is used.

In response to

pgsql-performance by date

Next:From: Carlo StonebanksDate: 2007-08-22 21:09:52
Subject: Re: Fast tsearch2, trigram matching on short phrases
Previous:From: Sachchida OjhaDate: 2007-08-22 20:54:29
Subject: Re: Long running transaction in pg_activity_log

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group