Re: [PATCH] initdb: Option description. - Mailing list pgsql-bugs

From David G Johnston
Subject Re: [PATCH] initdb: Option description.
Date
Msg-id 1417052516018-5828463.post@n5.nabble.com
Whole thread Raw
In response to Re: [PATCH] initdb: Option description.  (Mats Erik Andersson <bsd@gisladisker.se>)
List pgsql-bugs
Mats Erik Andersson wrote
> tisdag den 25 november 2014 klockan 13:52 skrev Magnus Hagander detta:
>> On Mon, Nov 17, 2014 at 12:12 AM, Mats Erik Andersson
>> <

> bsd@

> > wrote:
>> > Hello there,
>> >
>> > the recent introduction of new options `--auth-local'
>> > and `--auth-host' have lead to some confusion in the
>> > help massage for inetdb, leaving an erroneous `local'
>> > for `--auth' and `--auth-host'.  Please consider the
>> > following patch to improve the relevance.
>>
>> Hi!
>>
>> The idea behind the current wording is that it only sets the
>> authentication type for 127.0.0.1 and ::1 -- there is no entry in
>> pg_hba.conf generated for non-local TCP/IP connections. Perhaps we
>> could clarify it by saying "localhost TCP/IP" rather than "local
>> TCP/IP" though?
>
> Even admitting that the template is stated for localhost only,
> it seems clearer in my view to ignore this technicality in the
> message. Scaring the administrator slightly is no bad thing.

I might quibble on the specific wording but making it clear that initdb only
sets up locally accessible connections and permissions is accurate and
doesn't need to instill more FUD than it does currently.  If admins are
going to add non-local access they should consult the documentation and will
have to edit hba manually and should know that they are adding a trust
method for those non-local connections.  However, a user of initdb might not
be aware that such is being done for them by default and so the limited
warning there is useful.

David J.





--
View this message in context: http://postgresql.nabble.com/PATCH-initdb-Option-description-tp5827166p5828463.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Next
From: Tomas Vondra
Date:
Subject: Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)