Re: [PATCH] Explain what the default output_plugin_libraries do - Mailing list pgsql-hackers

Hi,

On Thu, Sep 10, 2026 at 9:47 AM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
>
> On Wed, Sep 9, 2026 at 5:43 AM Jacob Champion
> <jacob.champion@enterprisedb.com> wrote:
> > (The role of each builtin plugin should probably be
> > better explained in the documentation for output_plugin_libraries,
> > since this is a brand-new consideration for most people...)
>
> Splitting this concern off from the original report: I'd like to
> backpatch something like the attached so that it's more obvious why
> you might (or might not) want to keep those in the list in the first
> place.
>
> WDYT?

+1 to enhance the docs here. Overall it looks good to me. One nit:

1/ "publication slot creation" seems a bit confusing. How about we say
"Removing pgoutput from output_plugin_libraries will cause future
subscription connections and replication slot creations on the
publisher to fail."

+             Core plugin for logical replication. Removing
<literal>pgoutput</literal>
+             from <literal>output_plugin_libraries</literal> will cause future
+             subscription connections, and publication slot creation, to fail
+             with an error. (Beware that existing replication tools may not
+             degrade gracefully if the server is configured in this way.)

Just curious, do we need to backpatch this to all the supported
branches? Removing these can have consequences that show up later, so
backpatching makes sense to me.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com