From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | pgsql-docs(at)postgresql(dot)org |
Subject: | Remove recommendation for nightly VACUUM |
Date: | 2022-06-27 06:31:46 |
Message-ID: | 6f5e3da98fec14640f389d7b84c3b413833697f4.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
A customer recently pointed me to
https://www.postgresql.org/docs/current/sql-vacuum.html
and asked if I agree with the statement there that a nightly
scheduled VACUUM were a good idea:
"We recommend that active production databases be vacuumed frequently
(at least nightly), in order to remove dead rows. After adding or
deleting a large number of rows, it might be a good idea to issue a
VACUUM ANALYZE command for the affected table. This will update the
system catalogs with the results of all recent changes, and allow the
PostgreSQL query planner to make better choices in planning queries."
Looking at the Git history, most of that paragraph is from a time
when autovacuum did not yet exist or was much less reliable than it
is now. So I suggest removing all that and pointing to autovacuum
instead, as done in the attached patch.
Yours,
Laurenz Albe
Attachment | Content-Type | Size |
---|---|---|
0001-Remove-outdated-recommendation-for-manual-VACUUM.patch | text/x-patch | 2.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2022-06-27 08:31:43 | Re: Remove recommendation for nightly VACUUM |
Previous Message | Noboru Saito | 2022-06-27 05:13:54 | Re: proposal: convert comments in documents to html comments |