From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Doc: clarify introduction to database roles. |
Date: | 2023-03-26 18:48:16 |
Message-ID: | E1pgVPc-005WTe-1I@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Doc: clarify introduction to database roles.
Word-smith section 22.1 ("Database Roles") a little bit in hopes
of removing confusion about how the bootstrap superuser's name
is chosen.
While here, I couldn't help noticing that the claim that the bootstrap
superuser is the only initially-existing role has been a lie since
we started to invent predefined roles. We don't want too much detail
in this very introductory text, but it seems worth changing it to say
that it's the only initially-existing login-capable role.
Per documentation comment from Maja Zaloznik.
Discussion: https://postgr.es/m/167931662853.3349090.18217722739345182859@wrigleys.postgresql.org
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/6eefe2ce463f55bb3b8da7d561ad2f75053189e0
Modified Files
--------------
doc/src/sgml/user-manag.sgml | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-03-27 00:57:59 | pgsql: Generate pg_stat_get_xact*() functions for relations using macro |
Previous Message | Tom Lane | 2023-03-26 17:46:35 | Re: pgsql: Fix netmask handling in inet_minmax_multi_ops |