Re: initdb failure with Postgres 8.4.4

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: BRUSSER Michael <Michael(dot)BRUSSER(at)3ds(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: initdb failure with Postgres 8.4.4
Date: 2010-12-13 17:26:38
Message-ID: 4D06574E.2060907@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2010-12-13 17:34:35 Re: ALTER TABLE ... ADD FOREIGN KEY ... NOT ENFORCED
Previous Message Dmitriy Igrishin 2010-12-13 17:21:30 Re: hstores in pl/python