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

From BRUSSER Michael
Subject Re: initdb failure with Postgres 8.4.4
Date
Msg-id 29EA9BFEF7E7FC4F988818CA0C5C78C205AAEE@AG-DCC-MBX03.dsone.3ds.com
Whole thread Raw
In response to Re: initdb failure with Postgres 8.4.4  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: initdb failure with Postgres 8.4.4  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
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?

Michael



This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and
maybe confidential and/or privileged.  If you are not one of the named recipients or have received this email in error,
(i)you should not read, disclose, or copy it, (ii) please notify sender of your receipt by reply email and delete this
emailand all attachments, (iii) Dassault Systemes does not accept or assume any liability or responsibility for any use
ofor reliance on this email.For other languages, go to http://www.3ds.com/terms/email-disclaimer. 


pgsql-hackers by date:

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