That's what we had hoped.
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?
Thx
-----Original Message-----
From: Martijn van Oosterhout [mailto:kleptog@svana.org]
Sent: 24 November 2004 13:33
To: Francis Reed
Cc: 'pgsql-general@postgresql.org'
Subject: Re: [GENERAL] Moving/Using Postgres Binaries on multiple
machines
Sure, this is what Linux distributers do. They compile postgresql into
a binary package which is installed on the user's machine.
It works as long as the environments are reasonably compatable, all
have readline, similar libc, etc.
Hope this helps,
On Wed, Nov 24, 2004 at 12:30:28PM -0000, Francis Reed wrote:
> If I want to create a postgres database on multiple machines, is the
> practice of tarring or zipping up binaries compiled on one machine and
> untarring them on another, and using the binaries (initdb etc)
acceptable?.
> This removes the need for having a compiler and environment on the target
> machine, or is it necessary always to have such an environment on any
> machine you intend to use postgres on? Postgres seems to have enough
> environment options to allow this to work, overriding the original library
> locations and paths etc from the original machine on which postgres was
> compiled.
>
> Does anyone see a problem with this approach?
>
> Thanks!
>
> Francis
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.