Re: [PATCH] Explain what the default output_plugin_libraries do

On Fri, Sep 11, 2026 at 3:46 AM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
> Actually this thread was not split on the web archive ;-(. But the proposal is good.

Thanks for the review! Yeah, I think the archive just cares about
thread ID? My client isn't particularly smart when it comes to
those...

> 1.
> Wondering we need to add descriptions in logical-decoding.sgml. One idea is
> something like below, are there better ideas?

Possibly in a new "installation" section?

> ```
> + <entry>
> + Decodes the WAL stream into a human-readable text representation.
> + <xref linkend="app-pgrecvlogical"/> uses this plugin by default, so
> + removing it from <literal>output_plugin_libraries</literal> will
> + prevent the use of that utility unless a replacement plugin is
> + installed and explicitly selected with
> + <link linkend="app-pgrecvlogical-option-plugin"><literal>--plugin</literal></link>.
> + </entry>
> ```
>
> The description may not be accurate because the --plugin is referred only at the
> creation phase.

My goal on this particular page is only to highlight the command-line
incompatibility. The linked-to section for --plugin says

When creating a slot, use the specified logical decoding output plugin.
See Chapter 47. This option has no effect if the slot already exists.

which seems detailed enough to me; thoughts?

Thanks!
--Jacob