pgsql: Doc: Clarify the role of aggressive VACUUMs. - Mailing list pgsql-committers

From Peter Geoghegan
Subject pgsql: Doc: Clarify the role of aggressive VACUUMs.
Date
Msg-id E1najRh-0001dq-NI@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Doc: Clarify the role of aggressive VACUUMs.

Adjust the documentation's coverage of aggressive VACUUMs to make it
clearer that aggressive vacuuming isn't always strictly necessary.  It's
possible for non-aggressive VACUUMs to advance relfrozenxid/relminmxid
without fail, given the right workload conditions.

While this has always been true, it matters more with recent and pending
improvements to VACUUM.  These improvements make non-aggressive
vacuuming more likely to advance relfrozenxid/relminmxid in practice.
While this is an unrelated improvement to the docs, formally speaking,
it still doesn't seem worth backpatching.  So don't backpatch.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f7e4d5c64fb3977e3a773e7213472be1b59dab2f

Modified Files
--------------
doc/src/sgml/maintenance.sgml | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Add a couple more tests for interval input decoding.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix overflow hazards in interval input and output conversions.