postgres only in local socket

From: Developer <dev002(at)pas-world(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: postgres only in local socket
Date: 2009-04-28 11:34:00
Message-ID: 1240918440.18265.3.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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?

--

--
--
Publicidad y Servicios http://www.pas-world.com
Directorio http://www.precioventa.com
Tienda http://informatica.precioventa.com
Autoridad certificadora http://ca.precioventa.com
--
--

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tim Uckun 2009-04-28 11:36:24 Huge sample dataset for testing.
Previous Message Jasen Betts 2009-04-28 10:57:15 Re: No connection could be made because the target machine actively refused it