| 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:18:49 |
| Message-ID: | TY5PR01MB183143AB5B56D5A1439A4B87CF5812@TY5PR01MB18314.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Jacob,
> > + An output plugin must be installed as a dynamically loadable library in a
> > + location where the server can find it (see <xref
> linkend="xfunc-c-dynload"/>).
>
> I think we should explicitly recommend installation into the
> dynamic_library_path ($libdir for most people). Anything outside of
> dynamic_library_path couples clients to the directory layout, and it
> makes output_plugin_libraries maintenance harder/uglier.
+1, see attached v2.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-doc-clarify-the-location-where-output-plugin-must.patch | application/octet-stream | 1.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2026-09-24 05:21:27 | Re: Speed up lpad() and rpad() for one-byte padding strings |
| Previous Message | Michael Paquier | 2026-09-24 05:09:23 | Re: Reset waitStart when a lock wait fails |