Postgres Pro
Downloads
Home   >   mailing lists

Re: why local_preload_libraries does require a separate directory ? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: why local_preload_libraries does require a separate directory ?
Date
Msg-id 17796.1323033362@sss.pgh.pa.us
Whole thread Raw
In response to Re: why local_preload_libraries does require a separate directory ?  (Tomas Vondra <tv@fuzzy.cz>)
Responses Re: why local_preload_libraries does require a separate directory ?  (Tomas Vondra <tv@fuzzy.cz>)
List pgsql-hackers
Tree view 
Tomas Vondra <tv@fuzzy.cz> writes:
> On 3.12.2011 18:53, Tom Lane wrote:
>> Security: it lets the DBA constrain which libraries are loadable this way.

> But local_preload_libraries can be set only in postgresql.conf, right?

No.  It's PGC_BACKEND, which means it can be set at connection start by
a client (eg, via PGOPTIONS).

> The problem I'm trying to solve right now is that I do have an extension
> that needs to install two .so libraries - one loaded using
> shared_preload_libraries, one loaded using local_preload_libraries.

Um ... why would you design it like that?
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: cannot read pg_class without having selected a database / is this a bug?
Next
From: Tom Lane
Date:
Subject: Re: cannot read pg_class without having selected a database / is this a bug?