From: Tom Lane <tgl@sss.pgh.pa.us>
To: Cosimo Streppone <cosimo@streppone.it>
Cc: pgsql-performance@postgresql.org
Subject: Re: select count(*) on large tables
Date: Thu, 08 Apr 2004 10:09:07 -0400
Message-ID: <13441.1081433347@sss.pgh.pa.us> (raw)
In-Reply-To: <40751ED5.1010208@streppone.it>
References: <40751ED5.1010208@streppone.it>
Cosimo Streppone <cosimo@streppone.it> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, cosimo@streppone.it
Subject: Re: select count(*) on large tables
In-Reply-To: <13441.1081433347@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox