From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Michael Nolan" <htfoot(at)gmail(dot)com> |
Cc: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Listening on more than one port? |
Date: | 2006-08-31 14:14:46 |
Message-ID: | 7040.1157033686@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Michael Nolan" <htfoot(at)gmail(dot)com> writes:
> 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.
What I'd do is configure the firewall to forward connections to 5432 to
the production machine (port 5432) and forward connections to 5431 to
5432 on the devel server. There isn't any reason to have either
postmaster listening on multiple port numbers.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2006-08-31 14:17:51 | Re: Cutting the Gborg throat |
Previous Message | Magnus Hagander | 2006-08-31 13:58:41 | Re: Cutting the Gborg throat |