From 5e45211a64149b3c659b90ff2de6fa982a5a93ed Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:17:33 +0200 Subject: Adding upstream version 15.5. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/user-manag.html | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/src/sgml/html/user-manag.html (limited to 'doc/src/sgml/html/user-manag.html') diff --git a/doc/src/sgml/html/user-manag.html b/doc/src/sgml/html/user-manag.html new file mode 100644 index 0000000..b49ec9a --- /dev/null +++ b/doc/src/sgml/html/user-manag.html @@ -0,0 +1,20 @@ + +Chapter 22. Database Roles
Chapter 22. Database Roles
Prev UpPart III. Server AdministrationHome Next

Chapter 22. Database Roles

Table of Contents

22.1. Database Roles
22.2. Role Attributes
22.3. Role Membership
22.4. Dropping Roles
22.5. Predefined Roles
22.6. Function Security

+ PostgreSQL manages database access permissions + using the concept of roles. A role can be thought of as + either a database user, or a group of database users, depending on how + the role is set up. Roles can own database objects (for example, tables + and functions) and can assign privileges on those objects to other roles to + control who has access to which objects. Furthermore, it is possible + to grant membership in a role to another role, thus + allowing the member role to use privileges assigned to another role. +

+ The concept of roles subsumes the concepts of “users” and + “groups”. In PostgreSQL versions + before 8.1, users and groups were distinct kinds of entities, but now + there are only roles. Any role can act as a user, a group, or both. +

+ This chapter describes how to create and manage roles. + More information about the effects of role privileges on various + database objects can be found in Section 5.7. +

Prev Up Next
21.15. Authentication Problems Home 22.1. Database Roles
\ No newline at end of file -- cgit v1.2.3