From: | Doug McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | Francis Reed <freed(at)iel(dot)ie> |
Cc: | "'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 13:39:14 |
Message-ID: | 87oehn2wot.fsf@asmodeus.mcnaught.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Francis Reed <freed(at)iel(dot)ie> writes:
> 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?
I've had no problems doing this, though I generally standardize the
install location across multiple machines.
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Werdin Jens | 2004-11-24 13:53:31 | Performance |
Previous Message | Francis Reed | 2004-11-24 13:37:11 | Re: Moving/Using Postgres Binaries on multiple machines |