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

From Francis Reed
Subject Moving/Using Postgres Binaries on multiple machines
Date
Msg-id 14F834609826C748873A5012F5C13EAE7EEEED@dubmail2.iel.ie
Whole thread Raw
Responses Re: Moving/Using Postgres Binaries on multiple machines
Re: Moving/Using Postgres Binaries on multiple machines
Re: Moving/Using Postgres Binaries on multiple machines
List 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

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Insert may fail if i create a primary key on the oid
Next
From: "Ulrich Meis"
Date:
Subject: Can't get planner to use multicolumn index on large table