From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/role-removal.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/role-removal.html') diff --git a/doc/src/sgml/html/role-removal.html b/doc/src/sgml/html/role-removal.html index 0f64eeb..2af2c7d 100644 --- a/doc/src/sgml/html/role-removal.html +++ b/doc/src/sgml/html/role-removal.html @@ -1,5 +1,5 @@ -22.4. Dropping Roles
22.4. Dropping Roles
Prev UpChapter 22. Database RolesHome Next

22.4. Dropping Roles

+22.4. Dropping Roles

22.4. Dropping Roles
Prev UpChapter 22. Database RolesHome Next

22.4. Dropping Roles

Because roles can own database objects and can hold privileges to access other objects, dropping a role is often not just a matter of a quick DROP ROLE. Any objects owned by the role must @@ -51,4 +51,4 @@ DROP ROLE doomed_role; If DROP ROLE is attempted while dependent objects still remain, it will issue messages identifying which objects need to be reassigned or dropped. -

Prev Up Next
22.3. Role Membership Home 22.5. Predefined Roles
\ No newline at end of file +

Prev Up Next
22.3. Role Membership Home 22.5. Predefined Roles
\ No newline at end of file -- cgit v1.2.3