Re: Moving/Using Postgres Binaries on multiple machines - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: Moving/Using Postgres Binaries on multiple machines
Date
Msg-id 41A4B005.3080900@commandprompt.com
Whole thread Raw
In response to Re: Moving/Using Postgres Binaries on multiple machines  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
Peter Eisentraut wrote:

>Francis Reed wrote:
>
>
>>We tested the principle with postgres 7.4.6 but found a what we
>>believe is a compile time dependancy in create_conversion.sql where
>>$libdir is not being resolved properly during the initdb process on
>>the second machine. The usual environment variables don't seem to
>>help (LD_LIBRARY_PATH; PATH; PGLIB etc). Anyone come across that?
>>
>>
>
>Moving the installation to a different path is not supported for
>permanent use before 8.0.  You better try to install in the same
>directory layout on all machines where you want to deploy.
>
>
You can also use links, which is what we do. Mammoth Reokicator
automaticaly install in /usr/local/pgsql but we often put it
in /opt and we just link /usr/local/pgsql back.

Sincerely,

Joshua D. Drake







--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL


Attachment

pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: PostGreSQL upgrade failed (Debian Packages), need advice...
Next
From: Tom Lane
Date:
Subject: Re: pgdump of schema...