From 20452c325a161c09aa5ad50f055cc086e7ac3582 Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Tue, 21 Jan 2025 21:13:20 +0000 Subject: [PATCH] Fix external hyperlinks --- doc/src/architecture/users.m4 | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/src/architecture/users.m4 b/doc/src/architecture/users.m4 index 94584aa..e4a3a91 100644 --- a/doc/src/architecture/users.m4 +++ b/doc/src/architecture/users.m4 @@ -75,7 +75,7 @@ created. Ordinary interactions with the database, data entry, data retrieval, etc., should be done with a non-administrator login. -PostgreSQL_ also has a `superuser role`_.\ [#f4]_ +PostgreSQL_ also has a `superuser role`.\ [#f4]_ Superusers have permission to do anything with a database. As with the Unix ``root`` user, there should usually be only a single PostgreSQL_ role with superuser privileges.\ [#f1]_ @@ -123,9 +123,6 @@ change the database's structure, rule validation, and so forth. Developers are expected to have ordinary logins, for use when interacting with database content. -.. _superuser role: - https://www.postgresql.org/docs/current/role-attributes.html - .. rubric:: Footnotes .. [#f1] In environments where the PostgreSQL_ database is hosted and managed @@ -139,7 +136,7 @@ interacting with database content. .. [#f3] Developers are not in the ``pdb_role_owner`` group. .. [#f4] The Azure cloud platform does not allow logins (aka roles) to have - the ``SUPERUSER`` :ref:`role attribute `. + the ``SUPERUSER`` `role attribute`. Instead, the ``CREATEDB`` and ``CREATEROLE`` attributes are most that can be given. The SokweDB ``sdb_admin_group`` group (aka role) has ``CREATEDB`` @@ -150,3 +147,8 @@ interacting with database content. Membership in the ``sdb_admin_group`` role and having the role attributes ``CREATEROLE`` and ``CREATEDB`` is what grants a role (login) superuser privileges. + +.. _role attributes: + https://www.postgresql.org/docs/current/role-attributes.html + +.. _superuser role: role attributes_ -- 2.34.1