docs: small adjustements to recent SELECT and pg_upgrade improvements

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 72e3cb68c286b4ec85b91e0a6d5673de319ff544..afb2ff4fbb9cbf137d161422f4c44b493107ed40 100644 (file)
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -458,10 +458,10 @@ psql --username postgres --file script.sql postgres
     
      Once you are satisfied with the upgrade, you can delete the old
      cluster's data directories by running the script mentioned when
-     pg_upgrade completes. You can also delete the
-     old installation directories
-     (e.g. bin, share).  This will not work
-     if you have tablespaces inside the old data directory.
+     pg_upgrade completes. (Automatic deletion is not
+     possible if you have user-defined tablespaces inside the old data
+     directory.)  You can also delete the old installation directories
+     (e.g. bin, share).
     
    
 

diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index f1bc158d03bbd45654c165051856abe1e0089c92..231dc6ad8a3db3dddf591cb4b5f335485b7bba92 100644 (file)
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -1497,8 +1497,9 @@ SELECT * FROM name
     variant in parts of complex queries. Only the WITH,
     UNION, INTERSECT, EXCEPT,
     ORDER BY, LIMIT, OFFSET,
-    FETCH and locking clauses can be used with TABLE;
-    the WHERE clause and any form of aggregation cannot
+    FETCH and FOR locking clauses can be used
+    with TABLE; the WHERE clause and any form of
+    aggregation cannot
     be used.