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

From Craig Ringer
Subject Re: could not bind IPv4 socket
Date
Msg-id 49FA9550.9030005@postnewspapers.com.au
Whole thread Raw
In response to Re: could not bind IPv4 socket  (Greg Smith <gsmith@gregsmith.com>)
List pgsql-general
Greg Smith wrote:

> 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.

Just to expand on that:

listen_addresses is usually used if you want to do things like:

- Have the database running on a gateway host that's directly connected
to the Internet, but only permit connections to the database on the LAN
side, so even pre-auth exploits can't attack the database server from
the Internet side;

- Lock a cluster down to only be accessible from the local host, so
remote hosts can't even see it's running and can't attempt to talk to it; or

- Run multiple clusters on one host, each one bound to a different IP
address on the usual PostgreSQL port, so the machine hosting the
clusters looks like it's really multiple separate machines to outside users.

--
Craig Ringer

pgsql-general by date:

Previous
From: Andrew Maclean
Date:
Subject: Importing large objects from the client side programatically.
Next
From: Craig Ringer
Date:
Subject: Re: 08P01: unexpected EOF on client connection