From: | Tommi Maekitalo <t(dot)maekitalo(at)epgmbh(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Question regarding dynamic_library_path |
Date: | 2004-06-09 08:39:33 |
Message-ID: | 200406091039.33421.t.maekitalo@epgmbh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
in linux you can change LD_LIBRARY_PATH in a running process, but it does not
help. The library-loader initializes himself at process-startup and changing
LD_LIBRARY_PATH do not change the actual path, the process is using for
dlopen.
Tommi Mäkitalo
Am Dienstag, 8. Juni 2004 19:14 schrieb Thomas Hallgren:
> From: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
>
> > I think the idea is that you want to specify the path in the config
> > file, after the app has already started. I don't think you can modify
> > the environment variable after the app has started, and even if you can,
> > it seems simpler to just do it in our code and specify the exact path
> > rather than having it poke around in whatever LD_LIBRARY_PATH is set to.
>
> Ok, that makes sense. But I think most systems have the ability to change
> the environment of a running process (setenv on Posix systems) and the
> current design, simple as it is, doesn't work in all cases.
>
> regards,
>
> Thomas Hallgren
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2004-06-09 10:19:52 | Improving postgresql.conf |
Previous Message | SZŰCS Gábor | 2004-06-09 08:31:20 | simple_heap_update: tuple concurrently updated -- during INSERT |