Add missing documentation for PGC_SU_BACKEND in description of pg_settings.

Commit fe550b2ac249af5fbd8e9e19290a4ba43c882f2d missed updating this list
of the PGC_XXX values, which in hindsight is not so surprising because
catalogs.sgml is not a place you'd think to look for them.  In addition to
adding the missing doco, insert the PGC_XXX C enum names in SGML comments,
so that grepping for the enum names will find this file.  That might spare
the next person similar embarrassment.

Spotted by Magnus Hagander.

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 2325962e818884a884224a0c2d7e640579488e96..dfed546f5133b11d01ad6f794d6270960c7be3ae 100644 (file)
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -8833,6 +8833,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
 
   
    
+    
     internal
     
      
@@ -8844,6 +8845,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
     
    
    
+    
     postmaster
     
      
@@ -8857,6 +8859,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
     
    
    
+    
     sighup
     
      
@@ -8871,16 +8874,35 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
     
    
    
+    
+    superuser-backend
+    
+     
+      Changes to these settings can be made in
+      postgresql.conf without restarting the server.
+      They can also be set for a particular session in the connection request
+      packet (for example, via libpq's PGOPTIONS
+      environment variable), but only if the connecting user is a superuser.
+      However, these settings never change in a session after it is started.
+      If you change them in postgresql.conf, send a
+      SIGHUP signal to the postmaster to cause it to
+      re-read postgresql.conf.  The new values will only
+      affect subsequently-launched sessions.
+     
+    
+   
+   
+    
     backend
     
      
       Changes to these settings can be made in
-      postgresql.conf without restarting the server;
-      they can also be set for a particular session in the connection request
+      postgresql.conf without restarting the server.
+      They can also be set for a particular session in the connection request
       packet (for example, via libpq's PGOPTIONS
-      environment variable).  However, these settings never change in a
-      session after it is started.  If you change them in
-      postgresql.conf, send a
+      environment variable); any user can make such a change for his session.
+      However, these settings never change in a session after it is started.
+      If you change them in postgresql.conf, send a
       SIGHUP signal to the postmaster to cause it to
       re-read postgresql.conf.  The new values will only
       affect subsequently-launched sessions.
@@ -8888,6 +8910,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
     
    
    
+    
     superuser
     
      
@@ -8900,6 +8923,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
     
    
    
+    
     user