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, I'd
shutdown 8.0.3.

Thanks,
~DjK



---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

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 around if you
have a database which gets written to during your switchover time.


On Tue, 8 Nov 2005, Dan The Man wrote:

> 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, I'd shutdown
> 8.0.3.

--
Jeff Frost, Owner <jeff [at] frostconsultingllc.com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

you only need make postgres 8.1.0 run using another port, example 5438

2005/11/8, Dan The Man <bitsandbytes88 [at] hotmail.com>:
> 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 cou=
ld
> copy the data and support two databases until things looked good. Then, =
I'd
> shutdown 8.0.3.
>
> Thanks,
> ~DjK
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>


--
Atte

Moises Alberto Lindo Gutarra
Consultor y Desarrollador Java / Open Source
TUMI Solutions SAC
Tel: +51.13481104
Cel: +51.197366260
MSN : mlindo [at] tumisolutions.com

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

--=-ieyT3W/5rMaYLn+i8cOE
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

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, <r.m.guerrero [at] usit.uio.no>
Center for Information Technology Services
University of Oslo, Norway

PGP Public Key: http://folk.uio.no/rafael/

--=-ieyT3W/5rMaYLn+i8cOE
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQBDceQkBhuKQurGihQRAiLUAKCMPJWvw4BKIK6dPIuuOH/5zKA+QQCf WAvE
OMvSKU2CreK8thFsuSeL+xk=
=jX2n
-----END PGP SIGNATURE-----

--=-ieyT3W/5rMaYLn+i8cOE--

Rafael Martinez Guerrero <r.m.guerrero [at] usit.uio.no> 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 try to open /tmp/.s.PGSQL.5432 ...

You could maybe make the same-port trick work if you chroot one or both
postmasters, or relocate the socket directory to someplace besides /tmp,
but either of those approaches will make life difficult for clients
trying to make local non-TCP connections. On the whole, separate port
number is the path of least resistance in almost all cases.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

> 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)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match