X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id CDAE111F6662 for ; Wed, 19 Apr 2006 09:05:16 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.595 X-Spam-Level: X-Spam-Status: No, score=0.595 required=5 tests=[AWL=0.668, BAYES_00=-2.599, FORGED_RCVD_HELO=0.135, HTML_MESSAGE=0.001, MSGID_FROM_MTA_ID=1.393, SUBJ_ALL_CAPS=0.997] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id KMPMeFibVde4 for ; Wed, 19 Apr 2006 09:05:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sydney.mailnetwork.co.uk (server88-208-192-113.live-servers.net [88.208.192.113]) by postgresql.org (Postfix) with ESMTP id B01C611F60B4 for ; Wed, 19 Apr 2006 09:05:10 -0300 (ADT) Received: from [213.146.143.243] (port=22935 helo=it020361) by sydney.mailnetwork.co.uk with esmtpa (Exim 4.60) (envelope-from ) id 1FWBQg-0002Md-CS; Wed, 19 Apr 2006 13:05:06 +0100 Reply-To: From: "Andy Shellam" To: "'Rodrigo Sakai'" Cc: Subject: Re: IDLE IN TRANSACTION Date: Wed, 19 Apr 2006 13:05:06 +0100 Organization: the mail network MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01C663B1.E1C56890" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <004101c663a8$c5e65520$4700a8c0@TREEZANTHUS> Thread-Index: AcZjqPv9v21vYlBnRHmqcVh5g+Dv7AAADJrQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-Id: <20060419120510.B01C611F60B4@postgresql.org> X-Archive-Number: 200604/181 X-Sequence-Number: 21350 This is a multi-part message in MIME format. ------=_NextPart_000_001C_01C663B1.E1C56890 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit No problem really, all it means is the application has issued a start of transaction command, it just isn't doing anything at the moment. Transactions allow any data added during the application's running to be rolled back should, for example, the application crash - it'll prevent half-written data remaining stale in your database. My guess is when you Exit the application correctly, it'll issue a COMMIT statement to store the transactional data to your database. _____ From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Rodrigo Sakai Sent: 19 April 2006 1:00 pm 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! !DSPAM:14,4446269633691691718838! ------=_NextPart_000_001C_01C663B1.E1C56890 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

No problem really, all it means is = the application has issued a start of transaction command, it just = isn’t doing anything at the moment.

Transactions allow any data added during the application’s running = to be rolled back should, for example, the application crash – = it’ll prevent half-written data remaining stale in your = database.

My guess is when you Exit the = application correctly, it’ll issue a COMMIT statement to store the = transactional data to your database.

From: pgsql-admin-owner@postgresql.org = [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Rodrigo Sakai
Sent: 19 April 2006 1:00 = pm
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!

!DSPAM:14,4446269633691691718838!

------=_NextPart_000_001C_01C663B1.E1C56890--