On Thu, May 24, 2012 at 7:58 PM, Peter Eisentraut wrote:
> On tor, 2012-05-24 at 14:09 +0200, Magnus Hagander wrote:
>> Would i make sense to have a postgresql.conf parameter that would add
>> to LD_LIBRARY_PATH when loading libraries from
>> shared_preload_libraries (and other library loads).
>
>
On tor, 2012-05-24 at 14:09 +0200, Magnus Hagander wrote:
> Would i make sense to have a postgresql.conf parameter that would add
> to LD_LIBRARY_PATH when loading libraries from
> shared_preload_libraries (and other library loads).
Well, you could write a library that sets it in its init function
Peter Geoghegan writes:
> On 24 May 2012 13:09, Magnus Hagander wrote:
>> Would i make sense to have a postgresql.conf parameter that would add
>> to LD_LIBRARY_PATH when loading libraries from
>> shared_preload_libraries (and other library loads). To make it
>> possible to configure it without h
On 24 May 2012 13:22, Peter Geoghegan wrote:
> I found this blog post to be insightful:
>
> https://blogs.oracle.com/rie/entry/tt_ld_library_path_tt
This one might be more useful, and itself refers to the
aforementioned, earlier post:
https://blogs.oracle.com/ali/entry/avoiding_ld_library_path_t
On 24 May 2012 13:09, Magnus Hagander wrote:
> Would i make sense to have a postgresql.conf parameter that would add
> to LD_LIBRARY_PATH when loading libraries from
> shared_preload_libraries (and other library loads). To make it
> possible to configure it without having to mess around with the
Would i make sense to have a postgresql.conf parameter that would add
to LD_LIBRARY_PATH when loading libraries from
shared_preload_libraries (and other library loads). To make it
possible to configure it without having to mess around with the
operating system configuration? Or is that too much re
