aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-12-06 14:11:41 +0900
committerMichael Paquier <michael@paquier.xyz>2023-12-06 14:11:41 +0900
commit6248a2bb92ccd4c591437c415775ab3b34c61d4c (patch)
tree774896a4411d1c7663d245b7e5866451960745bd
parenta499c08dca5e0162e210cc8a411698e2808a04da (diff)
downloadpostgresql-6248a2bb92ccd4c591437c415775ab3b34c61d4c.tar.gz
postgresql-6248a2bb92ccd4c591437c415775ab3b34c61d4c.zip
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
-rw-r--r--src/backend/access/transam/xlog.c6
1 files changed, 4 insertions, 2 deletions
diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index 8b0710abe60..06235073ce5 100644
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -977,8 +977,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");