Re: initdb failure with Postgres 8.4.4 - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: initdb failure with Postgres 8.4.4
Date
Msg-id 4D06574E.2060907@dunslane.net
Whole thread Raw
In response to Re: initdb failure with Postgres 8.4.4  ("BRUSSER Michael" <Michael.BRUSSER@3ds.com>)
Responses Re: initdb failure with Postgres 8.4.4  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

On 12/13/2010 12:16 PM, BRUSSER Michael wrote:
> Here is what you should do:
>
> 1. Build Postgres with --prefix set to some empty directory.
> 2. Run install.
> 3. Bundle up the resulting install tree as part of your tarball.  Do not
> editorialize upon the relative locations of its contents.
> 4. Drop the install tree wherever you want on the target machine.
>
> -------------------------------------------------
>
> Would it be a completely crazy idea if I try to modify Postgres to look at some env. var
> (similar to PGDATA)  and if exists and path is valid look there for the timezone files?
>

Yes, that's only the first problem you have encountered. I predict there 
will be others if you go down this path. You are making life much harder 
for yourself than you need to. Just keep everything together and you'll 
be fine. If that's really impossible, use symlinks (or junction points 
on Windows) to achieve the same effect.

cheers

andrew


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: GiST insert algorithm rewrite
Next
From: David Fetter
Date:
Subject: Re: ALTER TABLE ... ADD FOREIGN KEY ... NOT ENFORCED