Avoid trying to write an empty WAL record in log_newpage_range().

tglsfdc · tglsfdc · commit 3e383f9b68f1 · 2023-04-17T14:22:26.000-04:00
If the last few pages in the specified range are empty (all zero), then log_newpage_range() could try to emit an empty WAL record containing no FPIs. This at least upsets an Assert in ReserveXLogInsertLocation, and might perhaps have bad real-world consequences in non-assert builds. This has been broken since log_newpage_range() was introduced, but the case was hard if not impossible to hit before commit 3d6a984 decided it was okay to leave VM and FSM pages intentionally zero. Nonetheless, it seems prudent to back-patch. log_newpage_range() was added in v12 but later back-patched, so this affects all supported branches. Matthias van de Meent, per report from Justin Pryzby Discussion: https://postgr.es/m/ZD1daibg4RF50IOj@telsasoft.com
diff --git a/src/backend/access/transam/xloginsert.c b/src/backend/access/transam/xloginsert.c
@@ -1304,6 +1304,10 @@ log_newpage_range(Relation rel, ForkNumber forknum,
 			blkno++;
 		}
 
+		/* Nothing more to do if all remaining blocks were empty. */
+		if (nbufs == 0)
+			break;
+
 		/* Write WAL record for this batch. */
 		XLogBeginInsert();
 

Original file line number	Diff line number	Diff line change
`@@ -1304,6 +1304,10 @@ log_newpage_range(Relation rel, ForkNumber forknum,`
`1304`	`1304`	`blkno++;`
`1305`	`1305`	`}`
`1306`	`1306`
	`1307`	`+ /* Nothing more to do if all remaining blocks were empty. */`
	`1308`	`+ if (nbufs == 0)`
	`1309`	`+ break;`
	`1310`	`+`
`1307`	`1311`	`/* Write WAL record for this batch. */`
`1308`	`1312`	`XLogBeginInsert();`
`1309`	`1313`