From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Doc: Clarify the role of aggressive VACUUMs. |
Date: | 2022-04-02 19:30:02 |
Message-ID: | E1najRh-0001dq-NI@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-04-02 20:12:39 | pgsql: Fix overflow hazards in interval input and output conversions. |
Previous Message | Tom Lane | 2022-04-02 17:50:21 | pgsql: Add a couple more tests for interval input decoding. |