RE: [PATCH] Explain what the default output_plugin_libraries do

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Jacob Champion' <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: 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-16 05:01:24
Message-ID: TYRPR01MB128457223C21E13F7639510D9F5B92@TYRPR01MB12845.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Jacob,

> > 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?

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?

> > 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?

After considering again, it might not be good to describe too detail in different
pages. So OK for me to retain.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-09-16 05:16:20 Re: remove_useless_joins vs. bug #19560
Previous Message Richard Guo 2026-09-16 04:56:34 Re: remove_useless_joins vs. bug #19560