Public bug reported:
Binary package hint: postgresql-common
The file /etc/cron.d/postgresql-common installed by the postgresql-
common package offers the following advice:
# On Sunday you may wish to run a VACUUM FULL ANALYSE as well
# If you do not run a 24/7 site, you may want to uncomment the next line
# so as to do a regular VACUUM FULL. If you need 24/7 connectivity, save
# VACUUM FULL for when you think you really need it.
# 10 3 * * Sun root if [ -x /usr/sbin/pg_maintenance ]; then
/usr/sbin/pg_maintenance --full --analyze >/dev/null; fi
I believe the general consensus of the Postgresql community is that
running "vacuum full" periodically against a database is rarely
considered a good idea as it can lead to issues like index bloat.
Perhaps this file should reflect that sentiment and point interested
people to the documentation on Postgresql's website so that they can
fully understand the impact that "vacuum full" can have on a database.
** Affects: postgresql-common (Ubuntu)
Importance: Undecided
Status: New
--
Documentation error in postgresql-common
https://bugs.launchpad.net/bugs/186831
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
