Skip site navigation (1) Skip section navigation (2)

Re: why local_preload_libraries does require a separate directory ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: why local_preload_libraries does require a separate directory ?
Date: 2011-12-04 21:16:02
Message-ID: 17796.1323033362@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tomas Vondra <tv(at)fuzzy(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-12-04 21:26:41
Subject: Re: cannot read pg_class without having selected a database / is this a bug?
Previous:From: Tomas VondraDate: 2011-12-04 21:04:40
Subject: Re: cannot read pg_class without having selected a database / is this a bug?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group