From: Rod Taylor <rbt@rbt.ca>
To: Josh Berkus <josh@agliodbs.com>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Christopher Browne <cbbrowne@libertyrms.info>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: count(*) slow on large tables
Date: Sun, 05 Oct 2003 15:11:50 -0400
Message-ID: <1065381109.23288.196.camel@jester> (raw)
In-Reply-To: <200310051157.21555.josh@agliodbs.com>
References: <200310041819.h94IJkV07596@candle.pha.pa.us>
<200310051157.21555.josh@agliodbs.com>
> And for those GUIs, wouldn't it be 97% as good to run an ANALYZE and give the
> approximate record counts for large tables?
Interfaces which run a COUNT(*) like that are broken by design. They
fail to consider the table may really be a view which of course could
not be cached with results like that and may take days to load a full
result set (we had some pretty large views in an old billing system).
Attachments:
signature.asc (application/pgp-signature, 186B) download
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: rbt@rbt.ca, josh@agliodbs.com, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, cbbrowne@libertyrms.info
Subject: Re: count(*) slow on large tables
In-Reply-To: <1065381109.23288.196.camel@jester>
* 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