Re: [PATCH] Explain what the default output_plugin_libraries do

On Tue, Sep 15, 2026 at 10:01 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
> > Possibly in a new "installation" section?
>
> Sounds good. Maybe we can clarify that the same loading mechanism is used as the
> C functions but no need to run CREATE EXTENSION and LOAD command, thought?

Sounds fine in concept (though I wouldn't necessarily want to backport
and/or skip beta review for this new section). Any recommended
wording?

> > 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?
>
> After considering again, it might not be good to describe too detail in different
> pages. So OK for me to retain.

Okay. Any thoughts on Bharath's note on "publication slot creation" above?

Thanks,
--Jacob