Re: Vaccuum best practice: cronjob or autovaccuum?

On Thu, Aug 28, 2008 at 9:47 AM, Joao Ferreira gmail
<joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com> wrote:
>
> http://www.postgresql.org/docs/8.3/static/maintenance.html
>
> you'll find that once in a while (start at once/week and build up or
> down from there) you can/should:
>
> - vacuum full
> - reindex your tables
> - reindex your indexes
>

Actually the manuals doesn't recomend VACUUM FULL for routine
maintenance anymore
"""
For those not using autovacuum, one approach is to schedule a
database-wide VACUUM once a day during low-usage period, supplemented
by more frequent vacuuming of heavily-updated tables if necessary.
(Some installations with extremely high update rates vacuum their
busiest tables as often as once every few minutes.) If you have
multiple databases in a cluster, don't forget to VACUUM each one; the
program vacuumdb might be helpful.

VACUUM FULL is recommended for cases where you know you have deleted
the majority of rows in a table, so that the steady-state size of the
table can be shrunk substantially with VACUUM FULL's more aggressive
approach. Use plain VACUUM, not VACUUM FULL, for routine vacuuming for
space recovery.
"""

--
regards,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. (593) 87171157