From: | "Kelly Burkhart" <kelly(at)kkcsm(dot)net> |
---|---|
To: | "Michael Nolan" <htfoot(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Listening on more than one port? |
Date: | 2006-08-31 02:50:17 |
Message-ID: | fa1e4ce70608301950h2974036dw9e080ba935845c01@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/30/06, Michael Nolan <htfoot(at)gmail(dot)com> wrote:
> 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.
Your firewall can probably redirect firewallhost:5431 to
insidehost:5432. If not, you could use something like simpleproxy on
insidehost to do what you want.
<http://sourceforge.net/projects/simpleproxy/>
-K
From | Date | Subject | |
---|---|---|---|
Next Message | Keith Hutchison | 2006-08-31 04:47:22 | pg_config --includedir is null |
Previous Message | Tim Allen | 2006-08-31 02:27:28 | Re: Postgresql mentioned on Newsforge MySQL article |