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 6B0B53A3D03 for ; Mon, 25 Oct 2004 06:36:44 +0100 (BST) 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 46900-04 for ; Mon, 25 Oct 2004 05:36:34 +0000 (GMT) Received: from trade-india.com (unknown [203.101.29.41]) by svr1.postgresql.org (Postfix) with SMTP id 3488D3A3B71 for ; Mon, 25 Oct 2004 06:36:33 +0100 (BST) Received: (qmail 4649 invoked from network); 25 Oct 2004 05:30:48 -0000 Received: from valium.trade-india-local.com (HELO ?192.168.0.100?) (192.168.0.100) by system66.trade-india-local.com with SMTP; 25 Oct 2004 05:30:48 -0000 Message-ID: <417C912E.3080109@trade-india.com> Date: Mon, 25 Oct 2004 11:07:50 +0530 From: Rajesh Kumar Mallah User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: ' in transaction' problem in mod_perl/DBI/DBD-Pg environment. Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/317 X-Sequence-Number: 15310 Hi, We run our webserver using mod_perl and perl/DBI/DBD-Pg . I have observed that most of the pg backends that block other queries are in ' in transaction' state. Usually sending a -INT or -TERM to such blocking backends solve the problem. My question is 1. Are there some precuation to be taken in perl/DBI programming in mod_perl environment to avoid backends getting into ' in transaction' mode? 2. Is it advisable/safe to run a daemon that TERMs such blocking backend at regular interval. 3. Most Importantly , If a do not have access to to the host is it possible to TERMinate such backeds from psql> Regds Mallah.