From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-bugs(at)postgreSQL(dot)org |
Subject: | Re: could not find /usr/local/timezone |
Date: | 2004-11-04 21:56:51 |
Message-ID: | 4973.1099605411@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Josh Berkus" <josh(at)agliodbs(dot)com> writes:
>> What it looks like is that the postmaster was executed out of
>> /usr/bin.
> dropping symlinks to the pg binaries in /usr/bin or
> /usr/local/bin or /sbin/ is something I've done for ages, on PostgreSQL
> versions 7.1 -> 7.4. Is there a problem with this now?
This is fundamentally broken by the changes to support relocatable
installs: PG now attempts to find the support files by relative paths
from the place where the executable was found.
It might be worth making find_my_exec able to detect that it found a
symlink, but I'm not sure how much code would have to be added to
resolve the symlink, nor how portable it would be. It would fail
anyway if someone did this via hard linking rather than symlink.
You could work around it by configuring the installation correctly,
ie, make --exec-prefix not be a sibling of the other install
directories. That would defeat the relocatable-install logic and
make it fall back to hardwired paths.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-11-05 00:04:58 | Re: could not find /usr/local/timezone |
Previous Message | Magnus Hagander | 2004-11-04 21:37:13 | Re: Bug in pgAdminIII or in pg 8 beta3 ? |