Re: could not bind IPv4 socket - Mailing list pgsql-general

From Greg Smith
Subject Re: could not bind IPv4 socket
Date
Msg-id alpine.GSO.2.01.0904302233450.151@westnet.com
Whole thread Raw
In response to could not bind IPv4 socket  (Grzegorz Buś <gall@p-team.org>)
Responses Re: could not bind IPv4 socket
Re: could not bind IPv4 socket
List pgsql-general
On Thu, 30 Apr 2009, Grzegorz Bu? wrote:

> listen_addresses = 'localhost,XXX.XXX.XXX.XXX'
> where XXX.XXX.XXX.XXX is IP address of remote client that I want to be able to use PostgreSQL server. Port is
default.

listen_addresses gets set to the IP address of the server itself, the IP
address it is "listening" for input on.  Since you're giving it a remote
address, that's why it can't create a socket to listen there.

There is a second file here, pg_hba.conf, that filters down who can
connect to the database.  Normal practice here is to set:

listen_address='*'

So that the server is remotely accessible from all of its interfaces, and
then you can do all filtering of who can connect just via pg_hba.conf
instead.  See
http://www.postgresql.org/docs/8.3/static/auth-pg-hba-conf.html for more
information.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: retrieving primary key for row with MIN function
Next
From: Craig Ringer
Date:
Subject: Re: How to begin to debug FATAL: invalid frontend message type 77 error messages?