| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: shared_preload_libraries path |
| Date: | 2012-05-24 14:36:00 |
| Message-ID: | 19737.1337870160@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Geoghegan <peter(at)2ndquadrant(dot)com> writes:
> 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 think the same. Aside from the problems Peter points out, there are
too many different ways to spell that variable name on different
platforms.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2012-05-24 14:37:04 | Re: Interrupting long external library calls |
| Previous Message | Peter Geoghegan | 2012-05-24 14:26:55 | Re: pg_stat_statments queryid |