From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dave Page" <dpage(at)postgresql(dot)org> |
Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, 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 22:02:09 |
Message-ID: | 4250.1196114529@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Dave Page" <dpage(at)postgresql(dot)org> writes:
> From: Peter Eisentraut <peter_e(at)gmx(dot)net>
>> 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.
I believe that that is talking specifically about shared libraries (or
DLLs in Windows-speak), and not about configuration or data files.
In particular, nothing under libdir would be a candidate to go under
sharedir, nor vice versa, since the former is supposed to hold
architecture-dependent files and the latter architecture-independent
files.
Mark hasn't been very clear about whether he wants to store static data
files or installation-changeable configuration info, so it's not clear
to me whether Peter's objection to using sharedir is appropriate or not.
But unless the files are architecture-sensitive (which they might be!),
libdir doesn't sound right in either case.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-26 22:07:59 | Re: 8.3devel slower than 8.2 under read-only load |
Previous Message | Tom Lane | 2007-11-26 21:04:18 | Re: [GENERAL] Empty arrays with ARRAY[] |