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

diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index 04d23bfe4a7ca4ecf407e4661da5835cf167b003..c15a720eb7aaac0e3291643d01bff5241bef24f7 100644 (file)
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -1235,8 +1235,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");