Re: count * performance issue

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: "sathiya psql" <sathiya(dot)psql(at)gmail(dot)com>
Cc: "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com>, "Mark Mielke" <mark(at)mark(dot)mielke(dot)cc>, pgsql-performance(at)postgresql(dot)org
Subject: Re: count * performance issue
Date: 2008-03-06 11:50:17
Message-ID: B94D3180-BB72-43EB-BA1E-90CF53705386@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On 6-Mar-08, at 1:43 AM, sathiya psql wrote:

> is there any way to explicitly force the postgres to use index scan
>
>

If you want to count all the rows in the table there is only one way
to do it (without keeping track yourself with a trigger ); a seq scan.

An index will not help you.

The only thing that is going to help you is really fast disks, and
more memory, and you should consider moving to 8.3 for all the other
performance benefits.

Dave

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dave Cramer 2008-03-06 12:13:57 Re: count * performance issue
Previous Message sathiya psql 2008-03-06 08:16:13 index usage makes problem