From: | "Dave Page" <dpage(at)postgresql(dot)org> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, "Mark Cave-Ayland" <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk> |
Subject: | Re: Locating sharedir in PostgreSQL on Windows |
Date: | 2007-11-26 20:45:03 |
Message-ID: | 200711262045040000@233658461 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> ------- Original Message -------
> From: Peter Eisentraut <peter_e(at)gmx(dot)net>
> To: Dave Page <dpage(at)postgresql(dot)org>
> Sent: 26/11/07, 20:14:25
> Subject: Re: [HACKERS] Locating sharedir in PostgreSQL on Windows
>
> Dave Page wrote:
> > How does that work with the stuff that goes into directories relative to
> > $libdir (per documented recommendations), without creating easy-to-break
> > paths like $libdir/../../MyAddon/8.3/MyAddon.dll?
>
> Which documented recommendation do you speak of?
>
http://www.postgresql.org/docs/8.3/static/xfunc-c.html states:
==========
It is recommended to locate shared libraries either relative to $libdir or through the dynamic library path. This simplifies version upgrades if the new installation is at a different location. The actual directory that $libdir stands for can be found out with the command pg_config --pkglibdir.
==========
That seems to have been there since at least 7.2.
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-26 21:04:18 | Re: [GENERAL] Empty arrays with ARRAY[] |
Previous Message | Brendan Jurd | 2007-11-26 20:42:21 | Re: [GENERAL] Empty arrays with ARRAY[] |