X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2EC9F56479 for ; Sun, 20 Mar 2005 23:35:51 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 49556-05 for ; Sun, 20 Mar 2005 23:35:49 +0000 (GMT) Received: from window.monsterlabs.com (window.monsterlabs.com [216.183.105.176]) by svr1.postgresql.org (Postfix) with SMTP id 9463856462 for ; Sun, 20 Mar 2005 23:35:47 +0000 (GMT) Received: (qmail 11103 invoked from network); 20 Mar 2005 23:35:50 -0000 Received: from host-209.149.56.238.nashville.net (HELO ?10.0.1.2?) (209.149.56.238) by 0 with SMTP; 20 Mar 2005 23:35:50 -0000 Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Message-Id: <0860bc19e1b883911bb20df78d6e26b9@sitening.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: PgSQL Admin From: Thomas F.O'Connell Subject: pgpool and ABORT Date: Sun, 20 Mar 2005 17:35:49 -0600 X-Mailer: Apple Mail (2.619.2) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/306 X-Sequence-Number: 16804 I'm using pgpool in a fairly high-traffic environment, and I regularly get this warning from pgpool calling ABORT: WARNING: there is no transaction in progress I found this post in the archives: http://archives.postgresql.org/pgsql-general/2004-04/msg01154.php But the README for pgpool asserts: Note that "ABORT" will not be issued if the backend is 7.4 or later and the session is not in a transaction block. I'm just curious why I'm still seeing the ABORTs if these sessions are not in a transaction block. I'm running postgres 7.4.6 and pgpool 2.5.1. -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-260-0005