Re: BUG #4787: Hardlink (ln) causes startup failure with bizarre "timezone_abbreviations" error

From: Mark <admin(at)asarian-host(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4787: Hardlink (ln) causes startup failure with bizarre "timezone_abbreviations" error
Date: 2009-05-02 22:27:52
Message-ID: 200905022227.n42MRq74026762@asarian-host.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, 02 May 2009 14:47:48 GMT, Tom Lane wrote

> Mark <admin(at)asarian-host(dot)net> writes:

> > 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:
>
> That's exactly what it already does, and why it would've worked
> if you'd used symlinks not hardlinks.

Interesting. Yet, as I reported earlier, whilst a symlink does seem to start
the server, pg_ctl takes a long time to do so, and then report: "could not
start server" anyway. But it actually *does* get started. So I figured maybe
something was not entirely right with the symlink, either.

- Mark

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-05-02 22:59:06 Re: BUG #4787: Hardlink (ln) causes startup failure with bizarre "timezone_abbreviations" error
Previous Message Kevin Field 2009-05-02 20:15:11 Re: BUG #4763: postgres service unstable, even during install