From 01b23daa9bab9648457935e0c24376637eecd2e4 Mon Sep 17 00:00:00 2001
From: Jeff Davis <jdavis@postgresql.org>
Date: Thu, 25 Aug 2022 10:26:31 -0700
Subject: [PATCH] Fix doc oversight for custom WAL resource managers.

Reported-by: Bharath Rupireddy
Backpatch-through: 15
Discussion: https://postgr.es/m/CALj2ACU+at7RqnWEzS59QsFg3ZOF4C4GSp7pt+PWiLEp0zrEKg@mail.gmail.com
---
 doc/src/sgml/tableam.sgml | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/tableam.sgml b/doc/src/sgml/tableam.sgml
index a4fed6ea577..6a6eb2b7665 100644
--- a/doc/src/sgml/tableam.sgml
+++ b/doc/src/sgml/tableam.sgml
@@ -87,11 +87,8 @@
   linkend="wal"><acronym>WAL</acronym></link>, or a custom implementation.
   If <acronym>WAL</acronym> is chosen, either <link
   linkend="generic-wal">Generic WAL Records</link> can be used,
-  or a new type of <acronym>WAL</acronym> records can be implemented.
-  Generic WAL Records are easy, but imply higher WAL volume.
-  Implementation of a new type of WAL record
-  currently requires modifications to core code (specifically,
-  <filename>src/include/access/rmgrlist.h</filename>).
+  or a <link linkend="custom-rmgr">Custom WAL Resource Manager</link> can be
+  implemented.
  </para>
 
  <para>