| From: | Mark Harrison <mh(at)pixar(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | constant time count(*) ? |
| Date: | 2003-10-15 18:00:10 |
| Message-ID: | 3F8D8B2A.60800@pixar.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
We're looking into moving some data from mysql to postgresql, and
notice that count(*) does not seem to be a constant-time function
as it seems to be in mysql.
planb=# explain select count(*) from assets;
QUERY PLAN
----------------------------------------------------------------
Aggregate (cost=22.50..22.50 rows=1 width=0)
-> Seq Scan on assets (cost=0.00..20.00 rows=1000 width=0)
(2 rows)
Is there a way to optimize count(*) such that it does not have
to do a sequential scan? We use this on some big tables and it
is slowing down processing quite a lot.
Thanks!
Mark
--
Mark Harrison
Pixar Animation Studios
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-10-15 18:21:57 | Re: Getting error codes for failed queries? |
| Previous Message | Rick Gigger | 2003-10-15 17:56:40 | Re: Porting Code to Postgresql |