Re: IDLE IN TRANSACTION - Mailing list pgsql-admin

From Chandra Sekhar Surapaneni
Subject Re: IDLE IN TRANSACTION
Date
Msg-id 0F7F9A82BB0DBB4396A9F8386D0E0612E1D2F7@pos-exch1.corp.positivenetworks.net
Whole thread Raw
In response to IDLE IN TRANSACTION  ("Rodrigo Sakai" <rodrigo.sakai@zanthus.com.br>)
List pgsql-admin
The Idle-in transaction process will prevent VACUUM from removing dead rows. I think you should have them fix the client such that they dont issue a begin unless they need to do something on the database. Also have the client commit as early as it can. It is safe to leave the database connection idle, but dont leave it idle in a transaction.
 
-Chandra Sekhar Surapaneni


From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Rodrigo Sakai
Sent: Wednesday, April 19, 2006 7:00 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] IDLE IN TRANSACTION

  Hi,
 
  I have an app developed with Delphi, and when I just start tha app it start a process (a connection) on the db server and the status stay 'IDLE IN TRANSACTION' until the end of the application. The app is developed by other people and I don't know much about how it was programmed! But I want to know if this kind of connection (idle in transaction) can cause locks and deadlocks on the db? And if is there a better way to connect to db?
 
  Thanks in advance!

pgsql-admin by date:

Previous
From: "Ma, Yi"
Date:
Subject: track alter table history
Next
From: "Rodrigo Sakai"
Date:
Subject: Re: IDLE IN TRANSACTION