postgres.git / summary / log / commit / refs

commit    7636725b922c8cd68f21d040f3542d3bce9c68a4
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Wed Dec 06 05:10:39 2023 +0000
First released in: 17.0, 13.14, 14.11, 15.6, 16.2

    Fix compilation on Windows with WAL_DEBUG
    
    This has been broken since b060dbe0001a that has reworked the callback
    mechanism of XLogReader, most likely unnoticed because any form of
    development involving WAL happens on platforms where this compiles fine.
    
    Author: Bharath Rupireddy
    Discussion: https://postgr.es/m/CALj2ACVF14WKQMFwcJ=3okVDhiXpuK5f7YdT+BdYXbbypMHqWA@mail.gmail.com
    Backpatch-through: 13


 src/backend/access/transam/xlog.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index 6526bd4f432..2d603d8dee2 100644
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -1029,8 +1029,10 @@ XLogInsertRecord(XLogRecData *rdata,
 
 		if (!debug_reader)
 			debug_reader = XLogReaderAllocate(wal_segment_size, NULL,
-											  XL_ROUTINE(), NULL);
-
+											  XL_ROUTINE(.page_read = NULL,
+														 .segment_open = NULL,
+														 .segment_close = NULL),
+											  NULL);
 		if (!debug_reader)
 		{
 			appendStringInfoString(&buf, "error decoding record: out of memory while allocating a WAL reading processor");


[parent: bfc677c3bc31]