On 8/30/06,
Martijn van Oosterhout <
kleptog@svana.org> wrote:
On Wed, Aug 30, 2006 at 02:42:58PM -0500, Michael Nolan wrote:
> I need to be able to have postmaster (8.1.2) listen on more than one port,
> eg, 5432 and some other port, such as 5431.
Why?
Situation in a nutshell:
Production and test databases are on two separate systems inside the firewall. The web server is at an ISP, outside the firewall.
The firewall sends all data coming from the ISP, port 5432 to a specific IP address inside the firewall: port 5432, which is the production serve.
Test transactions need to go to the other server, which has to be the same IP address (the address of the firewall), so it needs to be a different port, but I'm not sure if the port translator in the firewall will do any better at getting a response that than a port translator on the test server does.
However, I also need the test database responding to requests on port 5432.
Are you sure psql was using TCP? If you're connecting to the localhost
maybe it used UNIX domain sockets. It still needs a matching port
number there too...
Yes, I was using psql -h 10.x.x.x -p 5431 dbname username
--
Mike Nolan
> Is there a simple way to do this that I'm overlooking?
Address translation in the firewall?
Hope this helps,
--
Martijn van Oosterhout <kleptog@svana.org > http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFE9fByIB7bNG8LQkwRAtVTAJ9BzO0OAI7uUByKau+JzXPON4LckACdGg7x
rZMpNhhmIVFWqiVtDVQYSaw=
=X/3S
-----END PGP SIGNATURE-----