Re: Moving/Using Postgres Binaries on multiple machines

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Francis Reed <freed(at)iel(dot)ie>, "'Martijn van Oosterhout'" <kleptog(at)svana(dot)org>, "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Moving/Using Postgres Binaries on multiple machines
Date: 2004-11-24 16:00:05
Message-ID: 41A4B005.3080900@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL

Attachment Content-Type Size
jd.vcf text/x-vcard 285 bytes

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-11-24 16:05:14 Re: pgdump of schema...
Previous Message Joshua D. Drake 2004-11-24 15:58:50 Re: PostGreSQL upgrade failed (Debian Packages), need advice...