diff options
| author | Peter Geoghegan <pg@bowt.ie> | 2022-04-02 12:29:35 -0700 |
|---|---|---|
| committer | Peter Geoghegan <pg@bowt.ie> | 2022-04-02 12:29:35 -0700 |
| commit | f7e4d5c64fb3977e3a773e7213472be1b59dab2f (patch) | |
| tree | 7f5c34101772af925ff8c8ebf9605f49fcccb61e /src/backend/access/gist/gistvacuum.c | |
| parent | 1b208ebaf14e668a24c78ee42cf805431cd0f591 (diff) | |
| download | postgresql-f7e4d5c64fb3977e3a773e7213472be1b59dab2f.tar.gz postgresql-f7e4d5c64fb3977e3a773e7213472be1b59dab2f.zip | |
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.
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions