On 9.5.2012 22:50, Antonio Goméz Soto wrote: > Tomas, > > running vacuum full cdr brought down the query time to 4 seconds..
Fine. I'd recommend checking the other tables too - if this one was bloated, it's likely there might be others. Anyway, you should find out how this happened and fix it. This kind of bloat is usually caused by either frequent changes (updated / deletes) without sufficient vacuuming, or batch updates hitting many rows at once (e.g. during maintenance). Or maybe the vacuum was not running at all - I do remember there were frequent issues with free-space map. See this: http://www.varlena.com/GeneralBits/Tidbits/perf.html#maxfsmp http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server That should give you a good idea. Tomas -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
