pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Geoghegan <pg@bowt.ie>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Doc: update VACUUM FREEZE query conflict guidance.
Date: Mon, 08 May 2023 20:17:45 +0000
Message-ID: <E1pw7Im-00197e-Nd@gemulon.postgresql.org> (raw)

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.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/5698f07947396e1a7cd6564390306aafa26fc189

Modified Files
--------------
doc/src/sgml/high-availability.sgml | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)



Message-ID: <E1pw7Im-00197e-Nd@gemulon.postgresql.org>
Permalink:  ../E1pw7Im-00197e-Nd@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1pw7Im-00197e-Nd@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: pg@bowt.ie, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Doc: update VACUUM FREEZE query conflict guidance.
  In-Reply-To: <E1pw7Im-00197e-Nd@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox