summaryrefslogtreecommitdiff
path: root/src/bin/initdb/initdb.c
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2023-05-08 13:17:31 -0700
committerPeter Geoghegan <pg@bowt.ie>2023-05-08 13:17:31 -0700
commit5698f07947396e1a7cd6564390306aafa26fc189 (patch)
tree3dea5569eb51420ecd3b99e535617c435943c793 /src/bin/initdb/initdb.c
parentf7faa9976cc0504c027a20ed66ceca9018041dd4 (diff)
downloadpostgresql-5698f07947396e1a7cd6564390306aafa26fc189.tar.gz
Doc: update VACUUM FREEZE query conflict guidance.
Commit 1de58df4, which added page-level freezing, taught VACUUM to reuse each page's "set-visibility-map" snapshotConflictHorizon for freezing (at least in the vast majority of cases where freezing went ahead). This made VACUUM FREEZE much less prone to generating recovery conflicts on standbys; VACUUM FREEZE became only slightly more likely to cause recovery conflicts than an equivalent VACUUM. Update old documentation that specifically warned of the likelihood of recovery conflicts from VACUUM FREEZE. Explain the same general issue (the issue of VACUUM generating recovery conflicts even in the absence of dead row cleanup) using the example of conflicts caused by VISIBLE WAL records.
Diffstat (limited to 'src/bin/initdb/initdb.c')
0 files changed, 0 insertions, 0 deletions