> instance of postgres. Is there a way to keep my production db up and
> running in 8.0.3 while I also run 8.1.0 on the same server? Then, I could
Yes. There is a way. You have to specify another location and
port for 8.1.0.
Luf
---(end of broadcast)-
Rafael Martinez Guerrero <[EMAIL PROTECTED]> writes:
> On Tue, 2005-11-08 at 18:23, Moises Alberto Lindo Gutarra wrote:
>> you only need make postgres 8.1.0 run using another port, example 5438
> Or another IP/address (listen_addresses) and the same port 5432. ;)
No, because both postmasters will
On Tue, 2005-11-08 at 18:23, Moises Alberto Lindo Gutarra wrote:
> you only need make postgres 8.1.0 run using another port, example 5438
>
Or another IP/address (listen_addresses) and the same port 5432. ;)
--
Rafael Martinez, <[EMAIL PROTECTED]>
Center for Information Technology Services
Univ
Dan,
Sure, just bring it up in a different directory and have it listen on a
different port. You could either dump/restore to get the data over to it or
use a replication tool such as slony or mammoth to do the deed. The latter
method has the benefit of keeping it up to date while you poke a
you only need make postgres 8.1.0 run using another port, example 5438
2005/11/8, Dan The Man <[EMAIL PROTECTED]>:
> Hi,
> I have enough resources on my 3 postgresql servers to run more than one
> instance of postgres. Is there a way to keep my production db up and
> running in 8.0.3 while I also
Hi,
I have enough resources on my 3 postgresql servers to run more than one
instance of postgres. Is there a way to keep my production db up and
running in 8.0.3 while I also run 8.1.0 on the same server? Then, I could
copy the data and support two databases until things looked good. Then,
