X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D6801D1B53F for ; Fri, 14 Nov 2003 17:43:57 +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 29579-04 for ; Fri, 14 Nov 2003 13:43:27 -0400 (AST) Received: from fuji.krosing.net (silmet.estpak.ee [194.126.97.78]) by svr1.postgresql.org (Postfix) with ESMTP id 4D01DD1B51C for ; Fri, 14 Nov 2003 13:43:26 -0400 (AST) Received: from fuji.krosing.net (localhost.localdomain [127.0.0.1]) by fuji.krosing.net (8.12.8/8.12.8) with ESMTP id hAEHhSP5003241; Fri, 14 Nov 2003 19:43:28 +0200 Received: (from hannu@localhost) by fuji.krosing.net (8.12.8/8.12.8/Submit) id hAEHhSZd003239; Fri, 14 Nov 2003 19:43:28 +0200 X-Authentication-Warning: fuji.krosing.net: hannu set sender to hannu@tm.ee using -f Subject: Re: Help with count(*) From: Hannu Krosing To: Christopher Browne Cc: pgsql-performance@postgresql.org In-Reply-To: References: <200311141251.38786.mallah@trade-india.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1068831807.2540.44.camel@fuji.krosing.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 14 Nov 2003 19:43:27 +0200 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/115 X-Sequence-Number: 4675 Christopher Browne kirjutas R, 14.11.2003 kell 16:13: > Martha Stewart called it a Good Thing when mallah@trade-india.com (Rajesh Kumar Mallah) wrote: > > INFO: "profiles": found 0 removable, 369195 nonremovable row versions in 43423 pages > > DETAIL: 246130 dead row versions cannot be removed yet. > > Nonremovable row versions range from 136 to 2036 bytes long. > > It seems as though you have a transaction open that is holding onto a > whole lot of old rows. > > I have seen this happen somewhat-invisibly when a JDBC connection > manager opens transactions for each connection, and then no processing > happens to use those connections for a long time. The open > transactions prevent vacuums from doing any good... Can't the backend be made to delay the "real" start of transaction until the first query gets executed ? ------------ Hannu