Re: postgres only in local socket

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: Developer <dev002(at)pas-world(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: postgres only in local socket
Date: 2009-04-28 12:44:50
Message-ID: 20090428084450.7276ecc2.wmoran@potentialtech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In response to Developer <dev002(at)pas-world(dot)com>:

> Hello,
>
> In config:
>
> > # - Connection Settings -
> >
> > #listen_addresses = 'localhost' # what IP address(es) to listen on;
> > # comma-separated list of addresses;
> > # defaults to 'localhost', '*' = all
> > # (change requires restart)
> > #port = 5432 # (change requires restart)
> > max_connections = 100 # (change requires restart)
> > # Note: Increasing max_connections costs ~400 bytes of shared memory per.
> > # connection slot, plus lock space (see max_locks_per_transaction). You might
> > # also need to raise shared_buffers to support more connections.
> > #superuser_reserved_connections = 3 # (change requires restart)
> > #unix_socket_directory = '' # (change requires restart)
> > #unix_socket_group = '' # (change requires restart)
> > #unix_socket_permissions = 0777 # begin with 0 to use octal notation
> > # (change requires restart)
> > #bonjour_name = '' # defaults to the computer name
> >
>
>
> With something like this, I can see using netstat:
>
> > tcp 0 0 localhost.localdom:postgres *:* LISTEN
> >
>
>
> How to "listen" only in local socket?

Uncomment the listen line and fill it with a comma separated list of
IPs to listen on. Or take Jasen's advice, if that fits your need.

--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message A. Kretschmer 2009-04-28 12:46:36 Re: postgres only in local socket
Previous Message Jasen Betts 2009-04-28 12:40:58 Re: postgres only in local socket