Re: Database Select Slow

From: "(dot)ep" <erick(dot)papa(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Database Select Slow
Date: 2007-08-10 12:58:12
Message-ID: 1186750692.099717.150140@m37g2000prh.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Aug 10, 9:42 pm, andreas(dot)kretsch(dot)(dot)(dot)(at)schollglas(dot)com ("A.
Kretschmer") wrote:
> am Fri, dem 10.08.2007, um 17:46:11 +0800 mailte carter ck folgendes:
>
> > Hi all,
>
> > I am facing a performance issue here. Whenever I do a count(*) on a table
> > that contains about 300K records, it takes few minutes to complete. Whereas
> > my other application which is counting > 500K records just take less than
> > 10 seconds to complete.
>
> > I have indexed all the essential columns and still it does not improve the
> > speed.
>
> Indexes don't help in this case, a 'select count(*)' forces a seq. scan.
> Do you realy need this information? An estimate for the number of rows
> can you find in the system catalog (reltuples in pg_class, seehttp://www.postgresql.org/docs/current/interactive/catalog-pg-class.html)

Hi, what if I need to do a count with a WHERE condition? E.g.,

SELECT count(*) from customers where cust_id = 'georgebush' and
created_on > current_date - interval '1 week' ;

Can I get the info about this from somewhere in the pg system tables
as well? Queries like these are very common in most applications, so
I'm hoping I can avoid the sequential scans!

Many thanks for any tips.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bill Moran 2007-08-10 13:07:56 Re: Database Select Slow
Previous Message Marc Rossi 2007-08-10 12:45:23 Re: UPDATES hang every 5 minutes