RE: [PATCH] Explain what the default output_plugin_libraries do - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: [PATCH] Explain what the default output_plugin_libraries do
Date
Msg-id TY5PR01MB183143AB5B56D5A1439A4B87CF5812@TY5PR01MB18314.jpnprd01.prod.outlook.com
Whole thread
In response to Re: [PATCH] Explain what the default output_plugin_libraries do  (Jacob Champion <jacob.champion@enterprisedb.com>)
List 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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Reset waitStart when a lock wait fails
Next
From: John Naylor
Date:
Subject: Re: Speed up lpad() and rpad() for one-byte padding strings