Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit f66c825

Browse files
committed
Role membership of superusers is only by explicit membership for HBA.
Document that this rule applies to 'samerole' as well as to named roles. Per gripe from Tom Lane.
1 parent 84b8fca commit f66c825

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

doc/src/sgml/client-auth.sgml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -186,6 +186,10 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable>
186186
the requested user must be a member of the role with the same
187187
name as the requested database. (<literal>samegroup</> is an
188188
obsolete but still accepted spelling of <literal>samerole</>.)
189+
Superusers are not considered to be members of a role for the
190+
purposes of <literal>samerole</> unless they are explicitly
191+
members of the role, directly or indirectly, and not just by
192+
virtue of being a superuser.
189193
The value <literal>replication</> specifies that the record
190194
matches if a replication connection is requested (note that
191195
replication connections do not specify any particular database).

0 commit comments

Comments
 (0)