| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: shared_preload_libraries path |
| Date: | 2012-05-24 12:22:11 |
| Message-ID: | CAEYLb_WRf5o_i+drfYKeZtaF9br+ohxPEUgZyJ8RVLts_39bSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24 May 2012 13:09, Magnus Hagander <magnus(at)hagander(dot)net> 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
> operating system configuration? Or is that too much reimplementing OS
> functionality?
-1, I'm afraid.
I found this blog post to be insightful:
https://blogs.oracle.com/rie/entry/tt_ld_library_path_tt
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2012-05-24 12:29:41 | Re: shared_preload_libraries path |
| Previous Message | Magnus Hagander | 2012-05-24 12:19:50 | Re: pg_stat_statements temporary file |