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

From Bharath Rupireddy
Subject Re: [PATCH] Explain what the default output_plugin_libraries do
Date
Msg-id CALj2ACXaZzfYOjXv0L7B10mYKAe9aPcRKLDDMbkbjKZaW=Y4VA@mail.gmail.com
Whole thread
In response to Re: [PATCH] Explain what the default output_plugin_libraries do  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: [PATCH] Explain what the default output_plugin_libraries do
List pgsql-hackers
Hi,

On Mon, Sep 21, 2026 at 9:02 AM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
>
> > > Okay. Any thoughts on Bharath's note on "publication slot creation" above?
> >
> > I could not find the term "publication slot" in the existing doc, so I prefer
> > his idea. Another one I came up with to just simplify:
> >
> > ```
> > Removing from output_plugin_libraries will cause future logical replication to
> > fail with an error. (Beware that existing replication tools may not degrade gracefully
> > if the server is configured in this way.)
>
> But only built-in logical replication will fail. How about
>
>              Core plugin for logical replication. Removing
> <literal>pgoutput</literal>
>              from <literal>output_plugin_libraries</literal> will cause future
>              subscription connections, and maintenance of the replication slots
>              for subscriptions, to fail with an error. (Beware that ...
>
> ?

This part works for me. Thanks.

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



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Support for 8-byte TOAST values, round two
Next
From: Chao Li
Date:
Subject: Re: pg_walinspect: fix LSN validation messages and empty range handling