From 7b1e6302a182aa5cd460724f25d45f939e38a7e9 Mon Sep 17 00:00:00 2001 From: Vignesh C Date: Mon, 2 Nov 2026 11:25:02 +0530 Subject: [PATCH v1] Clarify full-page image behavior of REGBUF_NO_CHANGE in README 27caf4ca5ae stopped forcing a full-page image for REGBUF_NO_CHANGE buffers during wal_consistency_checking. This skips only the consistency-check image, not the full-page image used for torn-page protection. A full-page image is still taken on the first registration after a checkpoint, unless REGBUF_NO_IMAGE is also specified. Clarify this distinction in the README. --- src/backend/access/transam/README | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/backend/access/transam/README b/src/backend/access/transam/README index 595afa01fa7..22e3f971a8f 100644 --- a/src/backend/access/transam/README +++ b/src/backend/access/transam/README @@ -589,7 +589,8 @@ void XLogRegisterBuffer(uint8 block_id, Buffer buf, uint8 flags); The REGBUF_NO_CHANGE flag indicates that the buffer is registered without being modified by this record, and possibly without an exclusive content lock. wal_consistency_checking does not force a full-page image for such - a buffer. + a buffer. This does not affect full-page images used for torn-page + protection. void XLogRegisterData(const void *data, int len); -- 2.55.0