From 8209605966c330451314fe7899539fa40a4123d1 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 10 Oct 2023 15:27:26 -0400 Subject: [PATCH] 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 27c1f3d703..92a299d2d3 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; In order to bootstrap the database system, a freshly initialized system always contains one predefined login-capable role. This role - is always a superuser, and by default it will have + is always a superuser, and it will have the same name as the operating system user that initialized the - database cluster, unless another name is specified while - running initdb. - It is common, but not required, to arrange for this role to be named + database cluster with initdb unless a different name + is specified. This role is often named postgres. In order to create more roles you first have to connect as this initial role.