Moving/Using Postgres Binaries on multiple machines

From: Francis Reed <freed(at)iel(dot)ie>
To: "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: Moving/Using Postgres Binaries on multiple machines
Date: 2004-11-24 12:30:28
Message-ID: 14F834609826C748873A5012F5C13EAE7EEEED@dubmail2.iel.ie
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ulrich Meis 2004-11-24 12:33:04 Can't get planner to use multicolumn index on large table
Previous Message Richard Huxton 2004-11-24 11:42:53 Re: Insert may fail if i create a primary key on the oid