Re: QRY seems not using indexes - Mailing list pgsql-performance

From Qingqing Zhou
Subject Re: QRY seems not using indexes
Date
Msg-id dd9bm4$238b$1@news.hub.org
Whole thread Raw
Responses Re: QRY seems not using indexes  (Mark Kirkwood <markir@paradise.net.nz>)
List pgsql-performance
<morandell@gmail.com> writes
>
>
> so, if I do a qry like "EXPLAIN ANALYZE select * from pridecdr where
> idsede=8977758488" it tooks a lot of time before i get back any result:
>
> Index Scan using prd_id_sede on pridecdr  (cost=0.00..699079.90
> rows=181850 width=138) (actual time=51.241..483068.255 rows=150511
> loops=1)
>    Index Cond: (idsede = 8977758488::bigint)
>  Total runtime: 483355.325 ms
>

The query plan looks ok. Try to do EXPLAIN ANALYZE twice and see if there is
any difference. This could reduce the IO time to read your index/data since
you got enough RAM.

Also, if you haven't done VACUUM FULL for a long time, do so and compare the
difference.

Regards,
Qingqing



pgsql-performance by date:

Previous
From: "Steinar H. Gunderson"
Date:
Subject: Re: Why hash join instead of nested loop?
Next
From: Mark Kirkwood
Date:
Subject: Re: QRY seems not using indexes