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-17 08:42:06
Message-ID: TYRPR01MB128454D7506104D43AD54817BF5B82@TYRPR01MB12845.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Jacob,

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

Yes, this cannot be backported. How about attached?

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

Best regards,
Hayato Kuroda
FUJITSU LIMITED

Attachment Content-Type Size
kuroda.diffs application/octet-stream 1.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexandre Felipe 2026-09-17 08:43:04 Re: pg_regress: schedule multi-line test groups
Previous Message Vik Fearing 2026-09-17 08:39:22 Re: Logical Implication