Skip to content

Commit 8209605

Browse files
committed
doc: clarify how the bootstrap user name is chosen
Discussion: https://postgr.es/m/167931662853.3349090.18217722739345182859@wrigleys.postgresql.org Backpatch-through: 16
1 parent 7454502 commit 8209605

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

doc/src/sgml/user-manag.sgml

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -103,11 +103,10 @@ SELECT rolname FROM pg_roles WHERE rolcanlogin;
103103
<para>
104104
In order to bootstrap the database system, a freshly initialized
105105
system always contains one predefined login-capable role. This role
106-
is always a <quote>superuser</quote>, and by default it will have
106+
is always a <quote>superuser</quote>, and it will have
107107
the same name as the operating system user that initialized the
108-
database cluster, unless another name is specified while
109-
running <command>initdb</command>.
110-
It is common, but not required, to arrange for this role to be named
108+
database cluster with <command>initdb</command> unless a different name
109+
is specified. This role is often named
111110
<literal>postgres</literal>. In order to create more roles you
112111
first have to connect as this initial role.
113112
</para>

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy