Using Different Ports for Multiple PosgreSQL Installations: Any Issues?

[Tom Browder]

I'm investigating various methods for long-term upgrade capability of
my current PG setup and I want to assign an unused port to each
upgrade--such port being unique while the version exists on my system.

Has anyone found such a use causing any problems?

Thanks.

Best regards,

-Tom

[Ye Chuah]

I run multiple instances of postgres on unix sockets without any
problems. Do you have to use a port? If not, just use the sockets.

Cheers
Ye

Post by Tom Browder
I'm investigating various methods for long-term upgrade capability of
my current PG setup and I want to assign an unused port to each
upgrade--such port being unique while the version exists on my system.
Has anyone found such a use causing any problems?
Thanks.
Best regards,
-Tom
--
http://www.postgresql.org/mailpref/pgsql-novice

[Tom Browder]

Post by Ye Chuah
I run multiple instances of postgres on unix sockets without any
problems. Do you have to use a port? If not, just use the sockets.

Hm, I need remote access so I think I have to use a port, correct?

And really, I won't be using more than one instance except for a short
while during the upgrade of the data.

Thanks, Ye.

-Tom

[Bruce Momjian]

Post by Tom Browder

Post by Ye Chuah
I run multiple instances of postgres on unix sockets without any
problems. Do you have to use a port? If not, just use the sockets.

Hm, I need remote access so I think I have to use a port, correct?
And really, I won't be using more than one instance except for a short
while during the upgrade of the data.

FYI, the postgresql.conf port setting actually controls the TCP port and
is embedded in the unix domain socket name, so port really controls
both.
--
Bruce Momjian <***@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

[Tom Browder]

Post by Bruce Momjian

Post by Tom Browder

Post by Ye Chuah
I run multiple instances of postgres on unix sockets without any
problems. Do you have to use a port? If not, just use the sockets.

Hm, I need remote access so I think I have to use a port, correct?

...

Post by Bruce Momjian
FYI, the postgresql.conf port setting actually controls the TCP port and
is embedded in the unix domain socket name, so port really controls
both.

Thanks, Bruce.

Best,

-Tom

[Andrej]

Post by Tom Browder

Post by Bruce Momjian
FYI, the postgresql.conf port setting actually controls the TCP port and
is embedded in the unix domain socket name, so port really controls
both.

Thanks, Bruce.

As an aside: this is exactly the way postgres package maintainers for Debian/
*buntu tackle the issue of data migrations. Two versions running in
parallel on
different ports.


Cheers,
Andrej