Update or remove mentions of versions where appropriate.

diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml
index 1dc633ce9d186a610e25509f80512292bb18aa23..71f26d1c5fad7dbf29ce23043400da3996dd3886 100644 (file)
--- a/doc/src/sgml/ref/create_trigger.sgml
+++ b/doc/src/sgml/ref/create_trigger.sgml
@@ -1,5 +1,5 @@
 
 
@@ -150,7 +150,7 @@ CREATE
     Only the relation owner may create a trigger on this relation.
    
    
-    As of the current release (v7.0), STATEMENT triggers are not implemented.
+    As of the current release, STATEMENT triggers are not implemented.
    
    
     Refer to DROP TRIGGER for information on how to 

diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml
index a3b49bc3f6f4f705a59369d01915427efbc9d502..2a4fe7122018aaa095732e6dc9066a3b18ae45d1 100644 (file)
--- a/doc/src/sgml/ref/psql-ref.sgml
+++ b/doc/src/sgml/ref/psql-ref.sgml
@@ -1,5 +1,5 @@
 
 
@@ -1051,7 +1051,7 @@ lo_import 152801
 
    
    
-   As of psql version 7.0 it is no longer
+   In the current version, it is no longer
    necessary to save the command history, since that will be done
    automatically on program termination. The history is
    also loaded automatically every time psql
@@ -1579,7 +1579,7 @@ Access permissions for database "test"
       
 
       
-      As of version 7.0, psql automatically issues a
+      In the current version, psql automatically issues a
       password prompt whenever the backend requests password authentication.
       Because this is currently based on a hack, the automatic
       recognition might mysteriously fail, hence this option to force a prompt.

diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index 4d95b26e034f421acc72c4f7a26fe184d7227dfd..b6bbd7e5d1eedcad9458b2a30781b04f192a8a1d 100644 (file)
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -1,5 +1,5 @@
 
 
@@ -122,8 +122,8 @@ where from_item can be:
    table is scanned.  If ONLY is not specified, the table and all its
    descendant tables (if any) are scanned.  * can be appended to the
    table name to indicate that descendant tables are to be scanned,
-   but as of Postgres 7.1 this is the default
-   behavior.  (In releases before 7.1, ONLY was the default behavior.)
+   but in the current version, this is the default behavior.
+   (In releases before 7.1, ONLY was the default behavior.)