postgres.git / summary / log / commit / refs

commit    b01a5e71d89e8bc674d609bf52702008e73c0859
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Tue Oct 10 19:27:26 2023 +0000
First released in: 17.0, 16.1

    doc:  clarify how the bootstrap user name is chosen
    
    Discussion: https://postgr.es/m/167931662853.3349090.18217722739345182859@wrigleys.postgresql.org
    
    Backpatch-through: 16


 doc/src/sgml/user-manag.sgml | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/user-manag.sgml b/doc/src/sgml/user-manag.sgml
index 27c1f3d7032..92a299d2d33 100644
--- a/doc/src/sgml/user-manag.sgml
+++ b/doc/src/sgml/user-manag.sgml
@@ -103,11 +103,10 @@ SELECT rolname FROM pg_roles WHERE rolcanlogin;
   <para>
    In order to bootstrap the database system, a freshly initialized
    system always contains one predefined login-capable role. This role
-   is always a <quote>superuser</quote>, and by default it will have
+   is always a <quote>superuser</quote>, and it will have
    the same name as the operating system user that initialized the
-   database cluster, unless another name is specified while
-   running <command>initdb</command>.
-   It is common, but not required, to arrange for this role to be named
+   database cluster with <command>initdb</command> unless a different name
+   is specified.  This role is often named
    <literal>postgres</literal>. In order to create more roles you
    first have to connect as this initial role.
   </para>


[parent: 63e7cac0199d]