From: | Mark <admin(at)asarian-host(dot)net> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #4787: Hardlink (ln) causes startup failure with bizarre "timezone_abbreviations" error |
Date: | 2009-05-02 07:54:38 |
Message-ID: | 200905020754.n427sc4d024319@asarian-host.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
-----Original Message-----
From: pgsql-bugs-owner(at)postgresql(dot)org
[mailto:pgsql-bugs-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: vrijdag 1 mei 2009 23:57
To: Mark; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #4787: Hardlink (ln) causes startup failure with
bizarre "timezone_abbreviations" error
> What I'm inclined to do is modify PostmasterMain so that immediately
> after find_my_exec, it checks that get_share_path returns the name of
> a readable directory.
I understand the rationale for relocatable packages. So, I guess hardlinks
are out. But, barring hardlinks, perhaps, in the existence of a symlink, a
simple 'readlink' function could be done to auto-correct PostgreSQL's
base-location? Ala:
char buf[1024];
ssizet_t len;
....
if ((len = readlink ("/usr/local/bin/pg_ctl", buf, sizeof(buf)-1)) != -1)
buf[len] = '\0';
Symlinks are used quite often, *especially* when dealing with relocatable
packages (read: that will likely not reside in /usr/local/, etc.). And it
would only requires two or three extra lines of code, no?
At any rate, I appreciate you looking into this.
- Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-05-02 14:47:17 | Re: BUG #4787: Hardlink (ln) causes startup failure with bizarre "timezone_abbreviations" error |
Previous Message | Tom Lane | 2009-05-01 21:56:13 | Re: BUG #4787: Hardlink (ln) causes startup failure with bizarre "timezone_abbreviations" error |