Search Postgresql Archives

Re: For index bloat: VACUUM ANALYZE vs REINDEX/CLUSTER

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

 



2007/9/18, Joshua D. Drake <jd@xxxxxxxxxxxxxxxxx>:
> If you overrun your max_fsm_pages then vacuum analyze IS NOT ENOUGH. If> you do not overrun your max_fsm_pages, yes vacuum analyze can deal with> the issue.
Are you sure? I have a situation where above is no true. postgresversion 8.1.8. while vacuum verbose says:
INFO:  free space map contains 2329221 pages in 490 relationsDETAIL:  A total of 2345744 page slots are in use (including overhead).2345744 page slots are required to track all free space.Current limits are:  10000000 page slots, 1000 relations, using 58698 KB.
... and we have constant problem with index bloat and need to REINDEXfrequently.
the database is very redundant and has quite hight data retention rate(it's an ecommerce site)

-- Filip Rembiałkowski
---------------------------(end of broadcast)---------------------------TIP 3: Have you checked our extensive FAQ?
               http://www.postgresql.org/docs/faq

[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