From: Bruno Wolff III <bruno@wolff.to>
To: Dror Matalon <dror@zapatec.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: count(*) slow on large tables
Date: Thu, 2 Oct 2003 14:39:05 -0500
Message-ID: <20031002193905.GD18417@wolff.to> (raw)
In-Reply-To: <20031002191547.GZ87525@rlx11.zapatec.com>
References: <20031002191547.GZ87525@rlx11.zapatec.com>
On Thu, Oct 02, 2003 at 12:15:47 -0700,
Dror Matalon <dror@zapatec.com> wrote:
> Hi,
>
> I have a somewhat large table, 3 million rows, 1 Gig on disk, and growing. Doing a
> count(*) takes around 40 seconds.
>
> Looks like the count(*) fetches the table from disk and goes through it.
> Made me wonder, why the optimizer doesn't just choose the smallest index
> which in my case is around 60 Megs and goes through it, which it could
> do in a fraction of the time.
Because it can't tell from the index if a tuple is visible to the current
transaction and would still have to hit the table to check this. So that
performance would be a lot worse instead of better.
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: bruno@wolff.to, dror@zapatec.com
Subject: Re: count(*) slow on large tables
In-Reply-To: <20031002193905.GD18417@wolff.to>
* 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