Re: pgNixInstaller: Making PostgreSQL relocatable - Mailing list pgsql-hackers

From Greg Stark
Subject Re: pgNixInstaller: Making PostgreSQL relocatable
Date
Msg-id 873bh9wtqz.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: pgNixInstaller: Making PostgreSQL relocatable  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgNixInstaller: Making PostgreSQL relocatable  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> Enver ALTIN <ealtin@parkyeri.com> writes:
> > Tom Lane wrote:
> >> s/doable/already done/, no?
> 
> > I did a Google search on "relocatable PostgreSQL" and the first 
> > result[1] said it's already done. Apparently it didn't work for me on 
> > Solaris 8 (linking problems). I'll be looking at it sometime today.
> 
> OK ... it's supposed to work to shift the whole installation tree to
> a new root, ie, paths to places like the /share and /lib directories
> are determined relative to where the backend executable actually is.
> If this is not working on Solaris then for sure we want to know ...

I'm sure this isn't the only possible gotcha but I do seem to recall that on
Solaris there's no such thing as a default LD_LIBRARY_PATH. Every binary
stores absolute paths to every shared library it's linked against.

-- 
greg



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Get explain output of postgresql in Tables
Next
From: Hannu Krosing
Date:
Subject: Re: Accessing schema data in information schema