Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit8209605

Browse files
committed
doc: clarify how the bootstrap user name is chosen
Discussion:https://postgr.es/m/167931662853.3349090.18217722739345182859@wrigleys.postgresql.orgBackpatch-through: 16
1 parent7454502 commit8209605

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>, andby defaultit 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)

[8]ページ先頭

©2009-2025 Movatter.jp