From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
To: | Jason L(dot) Buberel <jason(at)buberel(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Solutions for listening on multiple ports? |
Date: | 2007-10-09 16:35:09 |
Message-ID: | 0DCEEC57-A0F6-41C4-95DE-CC010F092A20@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Oct 9, 2007, at 11:22 AM, Jason L. Buberel wrote:
> Is there a 'generally accepted' best practice for enabling a single
> postgres instance to listen for client connections on more than one
> ip/port combination?
>
> As far as I can tell, the 'listen_address' and 'port' configuration
> variables can only accommodate single values:
>
> listen_address = 127.0.0.1
> port = 5432
>
> What I would like to simulate is Apache's notation:
>
> Listen: 127.0.0.1:5432
> Listen: 192.168.0.1:54824
> ...
>
> The force behind this is network security policies and such. I
> would prefer to not resort to kernel-level netfilter trickery to
> accomplish this, if possible.
You can separate listen addresses with commas:
listen_address = '127.0.0.1,192.168.0.1'
AFAIK, you only get one port per cluster.
Erik Jones
Software Developer | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-10-09 17:12:53 | Re: Solutions for listening on multiple ports? |
Previous Message | Jason L. Buberel | 2007-10-09 16:22:27 | Solutions for listening on multiple ports? |