diff options
| author | Magnus Hagander <magnus@hagander.net> | 2022-06-27 19:43:27 +0200 |
|---|---|---|
| committer | Magnus Hagander <magnus@hagander.net> | 2022-06-27 19:46:23 +0200 |
| commit | 27f953ea9901c08fb3e4064f9a31e07bc30c1e6d (patch) | |
| tree | 668fa13552fbb63379dd93f8f43d4bf06f46a658 | |
| parent | d28e26bbe288c786d8211d8c526c34c775170dea (diff) | |
| download | postgresql-27f953ea9901c08fb3e4064f9a31e07bc30c1e6d.tar.gz postgresql-27f953ea9901c08fb3e4064f9a31e07bc30c1e6d.zip | |
Remove outdated recommendation for manual VACUUM
We have had a working and tunable autovacuum
for at least a decade now, so remove the recommendation to
manually vacuum tables at least every night.
Autovacuum is now also triggered by INSERTs, so we can also
remove the recommendation to run VACUUM (ANALYZE) after lots
of INSERTs or DELETEs.
Instead, suggest using autovacuum by moving the respective
paragraph up to where the importance of VACUUM is emphasized.
Author: Laurenz Albe <laurenz.albe@cybertec.at>
Reviewed-By: Magnus Hagander, Peter Geoghegan
Discussion: https://postgr.es/m/6f5e3da98fec14640f389d7b84c3b413833697f4.camel@cybertec.at
| -rw-r--r-- | doc/src/sgml/ref/vacuum.sgml | 20 |
1 files changed, 5 insertions, 15 deletions
diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml index 3df32b58ee6..c582021d29d 100644 --- a/doc/src/sgml/ref/vacuum.sgml +++ b/doc/src/sgml/ref/vacuum.sgml @@ -377,15 +377,11 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ <replaceable class="paramet </para> <para> - 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 <command>VACUUM - ANALYZE</command> command for the affected table. This will update the - system catalogs with - the results of all recent changes, and allow the - <productname>PostgreSQL</productname> query planner to make better - choices in planning queries. + We recommend that all databases be vacuumed regularly in + order to remove dead rows. <productname>PostgreSQL</productname> includes + an <quote>autovacuum</quote> facility which can automate routine vacuum + maintenance. For more information about automatic and manual vacuuming, + see <xref linkend="routine-vacuuming"/>. </para> <para> @@ -413,12 +409,6 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ <replaceable class="paramet </para> <para> - <productname>PostgreSQL</productname> includes an <quote>autovacuum</quote> - facility which can automate routine vacuum maintenance. For more - information about automatic and manual vacuuming, see - <xref linkend="routine-vacuuming"/>. - </para> - <para> Each backend running <command>VACUUM</command> without the <literal>FULL</literal> option will report its progress in the <structname>pg_stat_progress_vacuum</structname> view. Backends running |