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 D8D2E5285B for ; Tue, 19 Jul 2005 23:44:52 -0300 (ADT) 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 40174-05 for ; Wed, 20 Jul 2005 02:44:43 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 922BE529A2 for ; Tue, 19 Jul 2005 23:44:42 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j6K2iZIH011431; Tue, 19 Jul 2005 22:44:35 -0400 (EDT) To: FM Cc: Mailing List Postgres-Admin Subject: Re: PGSQL 7.4.8 : idle in transaction problem In-reply-to: <42DD5955.8000501@lexum.umontreal.ca> References: <42DD5955.8000501@lexum.umontreal.ca> Comments: In-reply-to FM message dated "Tue, 19 Jul 2005 15:49:41 -0400" Date: Tue, 19 Jul 2005 22:44:35 -0400 Message-ID: <11430.1121827475@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200507/137 X-Sequence-Number: 18193 FM writes: > What is strange is that users on all DB (not only DB1) are affected by > the JBOSS . > I understand that it locked DB1 but why it also locked users on others DB ? You should define "locked" more carefully: exactly what behavior are you seeing that you don't like? If it's a matter of whether VACUUM removes rows or not, that's expected: open-transaction bookkeeping is done across the whole cluster. (This is not something simple to change, since we may have to consider transaction IDs in shared catalogs.) regards, tom lane