Re: [PATCH] Explain what the default output_plugin_libraries do

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Explain what the default output_plugin_libraries do
Date: 2026-09-21 22:45:32
Message-ID: CALj2ACXaZzfYOjXv0L7B10mYKAe9aPcRKLDDMbkbjKZaW=Y4VA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Mon, Sep 21, 2026 at 9:02 AM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-09-21 22:50:42 Re: pg_walinspect: fix LSN validation messages and empty range handling
Previous Message Bharath Rupireddy 2026-09-21 22:39:23 Re: Support for 8-byte TOAST values, round two