Re: initdb recommendations - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: initdb recommendations
Date
Msg-id 91f8272f-117f-2a04-862b-871a7b86eeed@2ndquadrant.com
Whole thread Raw
In response to Re: initdb recommendations  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: initdb recommendations  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
On 2019-07-11 21:34, Julien Rouhaud wrote:
>> Note that with this change, running initdb without arguments will now
>> error on those platforms: You need to supply either a password or select
>> a different default authentication method.
> Should we make this explicitly stated in the documentation?  As a
> reference, it's saying:
> 
> The default client authentication setup is such that users can connect
> over the Unix-domain socket to the same database user name as their
> operating system user names (on operating systems that support this,
> which are most modern Unix-like systems, but not Windows) and
> otherwise with a password. To assign a password to the initial
> database superuser, use one of initdb's -W, --pwprompt or -- pwfile
> options.

Do you have a suggestion for where to put this and exactly how to phrase
this?

I think the initdb reference page would be more appropriate than
runtime.sgml.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Implement uuid_version()
Next
From: Thomas Munro
Date:
Subject: Re: Bad canonicalization for dateranges with 'infinity' bounds