From: | "Chandra Sekhar Surapaneni" <chandu(at)positivenetworks(dot)net> |
---|---|
To: | "Rodrigo Sakai" <rodrigo(dot)sakai(at)zanthus(dot)com(dot)br>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: IDLE IN TRANSACTION |
Date: | 2006-04-19 18:14:41 |
Message-ID: | 0F7F9A82BB0DBB4396A9F8386D0E0612E1D2F7@pos-exch1.corp.positivenetworks.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Rodrigo Sakai
Sent: Wednesday, April 19, 2006 7:00 AM
To: pgsql-admin(at)postgresql(dot)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!
From | Date | Subject | |
---|---|---|---|
Next Message | Arnau | 2006-04-19 18:26:56 | Schema synchronization |
Previous Message | Sergio López | 2006-04-19 18:09:24 | problem installing 8.1.3 |