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 1f139fa74312da0f5b4ebaf6646946183c51dff7..60e3ae6e50626bfed20841b939ed362dd7cbdc99 100644 (file)
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -1246,8 +1246,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");