pgsql: Update outdated paragraphs in README on how bgwriter works

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Update outdated paragraphs in README on how bgwriter works
Date: 2026-11-19 14:18:00
Message-ID: E1xU2xb-00000000OPv-2t44@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Update outdated paragraphs in README on how bgwriter works

Since commit 82467f627bd4, it takes a share-exclusive lock rather than
share lock, and the note on missing hint bit updates is no longer
relevant.

Since 9.2, the bgwriter is no longer responsible for checkpoints.

nextVictimBuffer is an atomic variable now. Clarify the details of
what locks are taken.

Co-authored-by: Henrik TJ <henrik(at)0x48(dot)dk>
Discussion: https://www.postgresql.org/message-id/7ecd1d06-24ab-ec54-127c-93e4ec691b77@0x48.dk

Branch
------
master

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

Modified Files
--------------
src/backend/storage/buffer/README | 27 +++++++++------------------
1 file changed, 9 insertions(+), 18 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tomas Vondra 2026-11-19 14:34:53 pgsql: Fix FULL JOIN constant propagation with non-strict operands
Previous Message Peter Eisentraut 2026-11-19 14:16:38 pgsql: psql: Replace cancel_pressed with CancelRequested