Add glossary entries related to superusers

Extracted from a more ambitious patch.

Author: David G. Johnston 
Discussion: https://postgr.es/m/CAKFQuwZC4K0XYBm0bwBMDOZySBqhOSekDhLuaw4vPi+ozi8gqQ@mail.gmail.com

diff --git a/doc/src/sgml/adminpack.sgml b/doc/src/sgml/adminpack.sgml
index 1150b7f5bbedb664d50ddf41ecb621193d8f84e5..184e96d7a0c5e528c558579205aff5e7f6fd3461 100644 (file)
--- a/doc/src/sgml/adminpack.sgml
+++ b/doc/src/sgml/adminpack.sgml
@@ -12,7 +12,7 @@
   pgAdmin and other administration and management tools can
   use to provide additional functionality, such as remote management
   of server log files.
-  Use of all these functions is only allowed to the superuser by default but may be
+  Use of all these functions is only allowed to database superusers by default, but may be
   allowed to other users by using the GRANT command.
  
 

diff --git a/doc/src/sgml/glossary.sgml b/doc/src/sgml/glossary.sgml
index d6d0a3a8140cddf0d800ff773ad783cc62f79d55..93fb149d9a26299f18d79dd5c6a8907301fdb631 100644 (file)
--- a/doc/src/sgml/glossary.sgml
+++ b/doc/src/sgml/glossary.sgml
@@ -233,6 +233,25 @@
    
   
 
+  
+   Bootstrap superuser
+   
+    
+     The first user initialized in a
+     database cluster.
+    
+    
+     This user owns all system catalog tables in each database.  It is also the role
+     from which all granted permissions originate.  Because of these things, this
+     role may not be dropped.
+    
+    
+     This role also behaves as a normal
+     database superuser.
+    
+   
+  
+
   
    Cast
    
@@ -342,6 +361,23 @@
    
   
 
+  
+   Cluster owner
+   
+    
+     The operating system user that owns the
+     data directory
+     and under which the postgres process is run.
+     It is required that this user exist prior to creating a new
+     database cluster.
+    
+    
+     On operating systems with a root user,
+     said user is not allowed to be the cluster owner.
+    
+   
+  
+
   
    Column
    
@@ -475,12 +511,20 @@
      and their common static and dynamic metadata.
      Sometimes referred to as a
      cluster.
+     A database cluster is created using the
+      program.
     
     
      In PostgreSQL, the term
      cluster is also sometimes used to refer to an instance.
      (Don't confuse this term with the SQL command CLUSTER.)
     
+    
+     See also cluster owner,
+     the operating-system owner of a cluster,
+     and bootstrap superuser,
+     the PostgreSQL owner of a cluster.
+    
    
   
 
@@ -489,6 +533,19 @@
    
   
 
+  
+   Database superuser
+   
+    
+     A role having superuser status
+     (see ).
+    
+    
+     Frequently referred to as superuser.
+    
+   
+  
+
   
    Data directory
    
@@ -1577,6 +1634,16 @@
    
   
 
+  
+   Superuser
+   
+    
+     As used in this documentation, it is a synonym for
+     database superuser.
+    
+   
+  
+
   
    System catalog
    
@@ -1827,7 +1894,8 @@
    
     
      A role that has the
-     LOGIN privilege.
+     login privilege
+     (see ).
     
    
   

diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml
index 81588962980fa6c1958f103454618df2c2266ce8..2410330cd6c7858e9e5669894c321314d9e28eac 100644 (file)
--- a/doc/src/sgml/ref/initdb.sgml
+++ b/doc/src/sgml/ref/initdb.sgml
@@ -37,14 +37,13 @@ PostgreSQL documentation
   Description
   
    initdb creates a new
-   PostgreSQL database cluster.  A database
-   cluster is a collection of databases that are managed by a single
-   server instance.
+   PostgreSQL database cluster.
   
 
   
-   Creating a database cluster consists of creating the directories in
-   which the database data will live, generating the shared catalog
+   Creating a database cluster consists of creating the
+   directories in
+   which the cluster data will live, generating the shared catalog
    tables (tables that belong to the whole cluster rather than to any
    particular database), and creating the postgres,
    template1, and template0 databases.
@@ -196,7 +195,7 @@ PostgreSQL documentation
         initdb, but you can avoid writing it by
         setting the PGDATA environment variable, which
         can be convenient since the database server
-        (postgres) can find the database
+        (postgres) can find the data
         directory later by the same variable.
        
       
@@ -338,7 +337,7 @@ PostgreSQL documentation
       --pwfile=filename
       
        
-        Makes initdb read the database superuser's password
+        Makes initdb read the bootstrap superuser's password
         from a file.  The first line of the file is taken as the password.
        
       
@@ -374,12 +373,10 @@ PostgreSQL documentation
       --username=username
       
        
-        Selects the user name of the database superuser. This defaults
-        to the name of the effective user running
-        initdb. It is really not important what the
-        superuser's name is, but one might choose to keep the
-        customary name postgres, even if the operating
-        system user's name is different.
+        Selects the user name of the
+        boostrap superuser.
+        This defaults to the name of the
+        cluster owner.
        
       
      
@@ -390,7 +387,7 @@ PostgreSQL documentation
       
        
         Makes initdb prompt for a password
-        to give the database superuser. If you don't plan on using password
+        to give the bootstrap superuser. If you don't plan on using password
         authentication, this is not important.  Otherwise you won't be
         able to use password authentication until you have a password
         set up.