Re: Use "samehost" by default in pg_hba.conf?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Use "samehost" by default in pg_hba.conf?
Date: 2009-10-01 12:39:54
Message-ID: 4AC4A31A.1000007@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost wrote:
> * Jaime Casanova (jcasanov(at)systemguards(dot)com(dot)ec) wrote:
>
>> just my 2 cents. but i always wondered about the existence of
>> listen_addresses at all... to me the only reason it exists is to force
>> me to change 'localhost' to '*' after installing, something i always
>> do almost automaticaly =)
>>
>
> Try running two postmasters on the same box using the same port (but
> different IPs) w/o being able to control what IPs it listens on.
>
>
>

Right. listen_addresses replaced two previous settings: tcpip_socket and
virtual_host. And back before 8.0 the default setting was not to listen
on *any* IP address.

I'm inclined to think our default setting is about right. It is very
common to run an application on the same machine as the database server
it uses, and then there is no often need to adjust listen_addresses at all.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Albe Laurenz 2009-10-01 12:53:57 Re: Rejecting weak passwords
Previous Message Michael Meskes 2009-10-01 12:27:26 Re: CommitFest 2009-09, two weeks on