In response to "sathiya psql" <sathiya.psql@xxxxxxxxx>: > EXPLAIN ANALYZE SELECT count(*) from call_log_in_ram ; > QUERY > PLAN > ---------------------------------------------------------------------------------------------------------------------------------- > Aggregate (cost=90760.80..90760.80 rows=1 width=0) (actual time= > 6069.373..6069.374 rows=1 loops=1) > -> Seq Scan on call_log_in_ram (cost=0.00..89121.24 rows=3279119 > width=0) (actual time=0.012..4322.345 rows=3279119 loops=1) > Total runtime: 6069.553 ms > (3 rows) > > zivah=# EXPLAIN ANALYZE SELECT count(*) from call_log_in_ram ; > QUERY > PLAN > ---------------------------------------------------------------------------------------------------------------------------------- > Aggregate (cost=90760.80..90760.80 rows=1 width=0) (actual time= > 6259.436..6259.437 rows=1 loops=1) > -> Seq Scan on call_log_in_ram (cost=0.00..89121.24 rows=3279119 > width=0) (actual time=0.013..4448.549 rows=3279119 loops=1) > Total runtime: 6259.543 ms 6 seconds doesn't sound like an unreasonable amount of time to count 3 million rows. I don't see any performance issue here. What were your expectations? -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran@xxxxxxxxxxxxxxxxxxxxxxx Phone: 412-422-3463x4023 -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
