Skip site navigation (1) Skip section navigation (2)

Re: Listening on more than one port?

From: "Michael Nolan" <htfoot(at)gmail(dot)com>
To: "Shane Ambler" <pgsql(at)007marketing(dot)com>
Cc: "PostgreSQL Mailing lists" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Listening on more than one port?
Date: 2006-08-31 15:54:07
Message-ID: 4abad0eb0608310854q3735db80h2296511fc7f28a7e@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
I prefer to have my live and test databases on separate systems, if only
because each one takes up well over 100 GB of disk space.

Our hardware firewall doesn't support port changes, but I was able to get
the rinetd port redirector working to redirect 5431 to 5432 on the test
system..  (And it works with psql now, too, I'm not sure why it didn't work
before.)

So, I've got a solution that works for me.  Thanks, everyone.

That's '30' for this thread.  :-)
--
Mike Nolan

On 8/31/06, Shane Ambler <pgsql(at)007marketing(dot)com> wrote:
>
> Obviously the test section has separate configurations to the live section
> -
> simply have 2 databases defined in the same server 'ourlivedatabase' and
> 'ourtestdatabase'. This still gives one small login/config  setting that
> changes between live and dev.
>
> On 31/8/2006 12:20, "Kelly Burkhart" <kelly(at)kkcsm(dot)net> wrote:
>
> > 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
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: don't forget to increase your free space map settings
> >
>
> --
>
> Shane Ambler
> Postgres(at)007Marketing(dot)com
>
> Get Sheeky @ http://Sheeky.Biz
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

In response to

pgsql-general by date

Next:From: Joshua D. DrakeDate: 2006-08-31 16:11:52
Subject: Thought provoking piece on NetBSD
Previous:From: Tom LaneDate: 2006-08-31 15:52:34
Subject: Re: Strange error related to temporary tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group