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 F0D04D1D09F for ; Thu, 8 Apr 2004 11:09:05 -0300 (ADT) 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 44223-10 for ; Thu, 8 Apr 2004 11:09:06 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 677F3D1D097 for ; Thu, 8 Apr 2004 11:09:03 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i38E976Y013442; Thu, 8 Apr 2004 10:09:07 -0400 (EDT) To: Cosimo Streppone Cc: pgsql-performance@postgresql.org Subject: Re: select count(*) on large tables In-reply-to: <40751ED5.1010208@streppone.it> References: <40751ED5.1010208@streppone.it> Comments: In-reply-to Cosimo Streppone message dated "Thu, 08 Apr 2004 11:43:49 +0200" Date: Thu, 08 Apr 2004 10:09:07 -0400 Message-ID: <13441.1081433347@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/109 X-Sequence-Number: 6409 Cosimo Streppone writes: > Is there an estimate time for this issue to be resolved? Approximately never. It's a fundamental feature of Postgres' design. As noted by Dennis, you can look at the pg_class statistics if a recent estimate is good enough, or you can build user-level tracking tools if you'd rather have fast count(*) than concurrent update capability. But don't sit around waiting for the developers to "fix this bug", because it isn't a bug and it isn't going to be fixed. regards, tom lane