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-24 05:06:01
Message-ID: TY5PR01MB18314F8CE00A66382A5DD6ED0F5812@TY5PR01MB18314.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Jacob,

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

Sorry for late, LGTM.

Regarding the point raised by Chao, I have no strong opinion for both. But there
are cases that string in-between () can be a complete statement. Did it mean that
Jacob's one does not also break the existing rule?

Best regards,
Hayato Kuroda
FUJITSU LIMITED

Attachment Content-Type Size
image/png 42.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-09-24 05:09:23 Re: Reset waitStart when a lock wait fails
Previous Message Robert Treat 2026-09-24 03:51:20 Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten