From: | pgsql(at)mohawksoft(dot)com |
---|---|
To: | mlikharev(at)aurigin(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SELECT TAKES A LOOOONG TIME |
Date: | 2003-06-11 15:21:37 |
Message-ID: | 4734.68.162.220.216.1055344897.squirrel@mail.mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Hi,
> could somebody explain me please why following select
> SELECT docid FROM prod.guids
> GROUP BY docid HAVING( COUNT(docid) > 1 )
>
> taking 15 min on 2 Proc Box on 1M rows, where number of duplicates
> around 300K,
> and docid indexed and not null and char(16).
>
> May be I am doing something wrong?
> Thank you.
I would first perform an "explain" on the query to have the database show
you where it is spending its time.
Second, you are performing a full table scan. Try this:
select count(docid) from prod.guids
See how long that takes, that's about as fast as your system will handle
that query. If that query is fast, you may need to play with the tuning
parameters of PostgreSQL like "sort memory." Have you adjusted any
parameters in your postgresql.conf file?
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2003-06-11 15:39:07 | Re: Function returns composite type |
Previous Message | pgsql | 2003-06-11 15:16:29 | Re: PostgreSQL under Windows |