From: "BBI Edwin Punzalan" <edwin(at)bluebamboo(dot)ph>
> Thanks but whatever it does, it didn't work. :
> Do you think upgrading will fix this problem?
are you sure there is a problem here to solve ?
> Seq Scan on chatlogs (cost=0.00..27252.86 rows=271882 width=212) (actual
> time=12.24..13419.36 rows=257137 loops=1)
you see that the actual rowcount matches the estimate,
so the planner is not being misled by wrong statistics.
you realize that an indexscan is not allways faster than
sequential scan unless the number of rows are a small
percentage of the total number of rows
did you try to add a 'order by date' clause to your query ?
In response to
pgsql-performance by date
|Next:||From: Rodrigo Carvalhaes||Date: 2004-12-01 11:16:58|
|Subject: pg_restore taking 4 hours!|
|Previous:||From: Andrew McMillan||Date: 2004-12-01 08:23:30|
|Subject: Re: Using "LIMIT" is much faster even though, searching|