From 558bca29e22d6d86979bf5be3f8f4ecca272f916 Mon Sep 17 00:00:00 2001
From: Narek Galstyan <narekg@berkeley.edu>
Date: Wed, 4 Nov 2026 15:36:22 -0500
Subject: [PATCH 2/2] Document that generic WAL logs init fork pages

The generic WAL documentation said that no WAL record is emitted for
unlogged relations.  Init fork pages are now WAL-logged regardless,
since the init fork is used to reset the relation after a crash and on
a promoted standby.
---
 doc/src/sgml/generic-wal.sgml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/generic-wal.sgml b/doc/src/sgml/generic-wal.sgml
index 41f97ad7dc8..f4bf93a8b64 100644
--- a/doc/src/sgml/generic-wal.sgml
+++ b/doc/src/sgml/generic-wal.sgml
@@ -139,8 +139,13 @@
     <listitem>
      <para>
       For unlogged relations, everything works the same except that no
-      actual WAL record is emitted.  Thus, you typically do not need to do
-      any explicit checks for unlogged relations.
+      actual WAL record is emitted for pages other than those of the
+      initialization fork (<literal>INIT_FORKNUM</literal>), as written by
+      <link linkend="index-functions"><function>ambuildempty</function></link>.
+      Those are always WAL-logged, since the initialization fork is used to
+      reset the relation after a crash and on a promoted standby.  Thus, you
+      typically do not need to do any explicit checks for unlogged
+      relations.
      </para>
     </listitem>
 
-- 
2.50.1 (Apple Git-155)