| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(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 17:12:53 |
| Message-ID: | dcc563d10710091012j53bd55b8m6a67d5eea5ebe4bf@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/9/07, Jason L. Buberel <jason(at)buberel(dot)org> 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
As mentioned by someone else, you can have > 1 IP be listended to, but
only the one port. You could likely use port forwarding to accomplish
having pgsql listen on > 1 port. In linux you'd do this with
iptables.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Vinogradovs | 2007-10-09 17:41:06 | Re: PG_TRY(), PG_CATCH().... |
| Previous Message | Erik Jones | 2007-10-09 16:35:09 | Re: Solutions for listening on multiple ports? |