Search Postgresql Archives

Re: performance; disk bad or something?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Marcus Engene <mengpg2@xxxxxxxxx> writes:
>          ->  Index Scan using apa_item_common_x1 on apa_item_common aic  
> (cost=0.00..4956.68 rows=1174 width=8) (actual time=19.854..9557.606 
> rows=1226 loops=1)

If the table only has 12000 rows then it should never have used an index
scan here at all --- a plain seqscan is usually the best bet for
retrieving 10% of a table.  Are you using nondefault planner settings?

How big is the table physically (VACUUM VERBOSE output about it might
tell something)?

			regards, tom lane


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux