X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 6670CD1D299 for ; Sun, 15 Feb 2004 16:23:58 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 13257-08 for ; Sun, 15 Feb 2004 12:23:49 -0400 (AST) Received: from mail.securitylending.com (mail.securitylending.com [65.90.55.70]) by svr1.postgresql.org (Postfix) with ESMTP id A4298D1DA69 for ; Sun, 15 Feb 2004 12:23:48 -0400 (AST) Subject: idle in transaction From: Warren Little To: pgsql-admin@postgresql.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1076862212.3148.9.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 15 Feb 2004 09:23:32 -0700 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/223 X-Sequence-Number: 12397 We recently upgraded postgres from 7.3 to 7.4, along with the JDBC jar, and noticed all the backend processes/connections are left in the "idle in transaction" state where before they where left in the "idle" state. Has something changed in the 7.4 jdbc driver vs 7.3 which might be causing this? Note We call setAutoCommit(FALSE) on every connection when created. -- Warren Little Senior Vice President Secondary Marketing Security Lending Wholesale, LC www.securitylending.com Tel: 866-369-7763 Fax: 866-849-8082