This patch makes some SGML markup more consistent and makes a small

improvement to the SSL auth docs.

diff --git a/doc/src/sgml/problems.sgml b/doc/src/sgml/problems.sgml
index 3e31e559e41407dd7411bb0522dbe791d7a5eb91..02492a1febe2cb20a5d5406bbe6e97aa78b62609 100644 (file)
--- a/doc/src/sgml/problems.sgml
+++ b/doc/src/sgml/problems.sgml
@@ -1,5 +1,5 @@
 
 
 
@@ -18,7 +18,7 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql E
  
   The following suggestions are intended to assist you in forming bug reports
   that can be handled in an effective fashion. No one is required to follow
-  them but it tends to be to everyone's advantage.
+  them but doing so tends to be to everyone's advantage.
  
 
  
@@ -204,17 +204,19 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql E
 
     
      
-      Any command line options and other start-up options, including concerned
-      environment variables or configuration files that you changed from the
-      default. Again, be exact. If you are using a prepackaged
-      distribution that starts the database server at boot time, you should try
-      to find out how that is done.
+      Any command line options and other start-up options, including
+      any relevant environment variables or configuration files that
+      you changed from the default. Again, please provide exact
+      information. If you are using a prepackaged distribution that
+      starts the database server at boot time, you should try to find
+      out how that is done.
      
     
 
     
      
-      Anything you did at all differently from the installation instructions.
+      Anything you did at all differently from the installation
+      instructions.
      
     
 
@@ -234,9 +236,14 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql E
      
 
      
-      If your version is older than &version; we will almost certainly tell
-      you to upgrade. There are tons
-      of bug fixes in each new release, that is why we make new releases.
+      If your version is older than &version; we will almost certainly
+      tell you to upgrade. There are many bug fixes and improvements
+      in each new release, so it is quite possible that a bug you have
+      encountered in an older release of PostgreSQL
+      has already been fixed. We can only provide limited support for
+      sites using older releases of PostgreSQL; if you require more
+      than we can provide, consider acquiring a commercial support
+      contract.
      
      
      
@@ -244,12 +251,14 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql E
 
     
      
-      Platform information. This includes the kernel name and version, C library,
-      processor, memory information. In most cases it is sufficient to report
-      the vendor and version, but do not assume everyone knows what exactly
-      Debian contains or that everyone runs on Pentiums. If
-      you have installation problems then information about compilers, make,
-      etc. is also necessary.
+      Platform information. This includes the kernel name and version,
+      C library, processor, memory information, and so on. In most
+      cases it is sufficient to report the vendor and version, but do
+      not assume everyone knows what exactly Debian
+      contains or that everyone runs on Pentiums. If you have
+      installation problems then information about the toolchain on
+      your machine (compiler, make, and so
+      on) is also necessary.
      
     
    
@@ -269,7 +278,7 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.16 2003/11/29 19:51:37 pgsql E
   
 
   
-   When writing a bug report, please choose non-confusing terminology.
+   When writing a bug report, please avoid confusing terminology.
    The software package in total is called PostgreSQL,
    sometimes Postgres for short. If you
    are specifically talking about the backend server, mention that, do not

diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml
index d1a322633e0d9875aed21b9185058f21213dc5b6..e78ee548fc5a393508af76b5e6a56c612a16abec 100644 (file)
--- a/doc/src/sgml/ref/lock.sgml
+++ b/doc/src/sgml/ref/lock.sgml
@@ -1,5 +1,5 @@
 
 
@@ -108,9 +108,10 @@ where lockmode is one of:
      
 
      
-      The command LOCK a, b; is equivalent to
-      LOCK a; LOCK b;. The tables are locked one-by-one in
-      the order specified in the LOCK command.
+      The command LOCK TABLE a, b; is equivalent to
+      LOCK TABLE a; LOCK TABLE b;. The tables are locked
+      one-by-one in the order specified in the LOCK
+      TABLE command.
      
     
    
@@ -136,17 +137,18 @@ where lockmode is one of:
   Notes
 
    
-    LOCK ... IN ACCESS SHARE MODE requires SELECT
+    LOCK TABLE ... IN ACCESS SHARE MODE requires SELECT
     privileges on the target table.  All other forms of LOCK
     require UPDATE and/or DELETE privileges.
    
 
    
-    LOCK is useful only inside a transaction block
-    (BEGIN/COMMIT pair), since the lock is dropped
-    as soon as the transaction ends.  A LOCK command appearing
-    outside any transaction block forms a self-contained transaction, so the
-    lock will be dropped as soon as it is obtained.
+    LOCK TABLE is useful only inside a transaction
+    block (BEGIN/COMMIT pair), since the lock
+    is dropped as soon as the transaction ends.  A LOCK
+    TABLE command appearing outside any transaction block forms a
+    self-contained transaction, so the lock will be dropped as soon as
+    it is obtained.
    
 
   
@@ -157,7 +159,11 @@ where lockmode is one of:
    ROW EXCLUSIVE mode is a sharable table lock.  Keep in
    mind that all the lock modes have identical semantics so far as
    LOCK TABLE is concerned, differing only in the rules
-   about which modes conflict with which.
+   about which modes conflict with which. For information on how to
+   acquire an actual row-level lock, see 
+   and the 
+   endterm="sql-for-update-title"> in the SELECT
+   reference documentation.