From 5ff1c81a91ac4f4ff3401efedff0a3c17842bd6e Mon Sep 17 00:00:00 2001
From: Hayato Kuroda <kuroda.hayato@fujitsu.com>
Date: Thu, 24 Sep 2026 14:17:00 +0900
Subject: [PATCH v2] doc: clarify the location where output plugin must be

---
 doc/src/sgml/logicaldecoding.sgml | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml
index 6dc49108997..04d33543ec9 100644
--- a/doc/src/sgml/logicaldecoding.sgml
+++ b/doc/src/sgml/logicaldecoding.sgml
@@ -775,6 +775,25 @@ DETAIL:  Synchronization could lead to data loss, because the remote slot needs
    </sect2>
   </sect1>
 
+  <sect1 id="logicaldecoding-output-plugin-installing">
+   <title>Installing Logical Decoding Output Plugins</title>
+   <para>
+    An output plugin must be installed as a dynamically loadable library.  The
+    library should be installed in a directory listed in
+    <xref linkend="guc-dynamic-library-path"/>, so that the plugin can be
+    referenced by name without depending on an installation-specific directory
+    path (see <xref linkend="xfunc-c-dynload"/>).
+    The library is loaded automatically when the output plugin is used; neither
+    <link linkend="sql-load"><command>LOAD</command></link> nor
+    <link linkend="sql-createextension"><command>CREATE EXTENSION</command></link>
+    is required for this.
+   </para>
+   <para>
+    The library's name must also be listed in
+    <xref linkend="guc-output-plugin-libraries"/>.
+   </para>
+  </sect1>
+
   <sect1 id="logicaldecoding-output-plugin-writing">
    <title>Writing Logical Decoding Output Plugins</title>
    <para>
-- 
2.52.0