Get rid of the little "v"s in front of version numbers, substituting the

full word "version" where appropriate.

diff --git a/doc/src/sgml/arch-dev.sgml b/doc/src/sgml/arch-dev.sgml
index 37b09c196ee6d988f91694830380267fd86db5ea..3c37e6e0c5c5aa7fe47bee5ffc6d23b87a6a513d 100644 (file)
--- a/doc/src/sgml/arch-dev.sgml
+++ b/doc/src/sgml/arch-dev.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -1724,7 +1724,7 @@ havingQual} to the one attached to the field {\tt havingQual} of the
 {\it parsetree} given by the parameter {\tt parsetree}. This is done
 by adding a new {\tt AND} node and attaching the old and the new {\it
 operator tree} as arguments to it. {\tt AddHavingQual()} has not been
-existing until v6.3.2. It has been created for the {\it having logic}.
+existing until version 6.3.2. It has been created for the {\it having logic}.
 %
 \begin{verbatim}
   void
@@ -1752,7 +1752,7 @@ existing until v6.3.2. It has been created for the {\it having logic}.
 This function is similar to the above described function  {\tt
 AddHavingQual()}. It also adds the {\it operator tree} given by the
 parameter {\tt havingQual} but prefixes it by a {\tt NOT} node. {\tt
-AddNotHavingQual()} has also not been existing until v6.3.2 and has been
+AddNotHavingQual()} has also not been existing until version 6.3.2 and has been
 created for the {\it having logic}.
 %
 \begin{verbatim}

diff --git a/doc/src/sgml/cvs.sgml b/doc/src/sgml/cvs.sgml
index 2c2b514d88aaaf08353858dce956ab15f0df8009..861633490eea00091ce01a0cb1cd9044da4a5985 100644 (file)
--- a/doc/src/sgml/cvs.sgml
+++ b/doc/src/sgml/cvs.sgml
@@ -1,5 +1,5 @@
 
@@ -99,7 +99,7 @@ $ cvs checkout -r REL6_4 tc
   
 
   
-   So, to create the v6.4 release
+   So, to create the 6.4 release
    I did the following:
 
    

diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml
index 35f930b33b5acf2eb25da5e2c73418661bb23699..06726fb1ff33c3db2175edf97aa83eb33d6dd398 100644 (file)
--- a/doc/src/sgml/datetime.sgml
+++ b/doc/src/sgml/datetime.sgml
@@ -1,5 +1,5 @@
 
 
@@ -622,7 +622,7 @@ Date/time details
    Gregorian years 1-99AD may be entered by using 4 digits with leading
    zeros (e.g. 0099 is 99AD). Previous versions of
    Postgres accepted years with three
-   digits and with single digits, but as of v7.0 the rules have
+   digits and with single digits, but as of version 7.0 the rules have
    been tightened up to reduce the possibility of ambiguity.
        
       

diff --git a/doc/src/sgml/history.sgml b/doc/src/sgml/history.sgml
index 149928232610679398c67504fa38ffd34243efc6..fe2168cb07424e107dae0cd86c0aed7bcf751495 100644 (file)
--- a/doc/src/sgml/history.sgml
+++ b/doc/src/sgml/history.sgml
@@ -1,5 +1,5 @@
 
 
 
@@ -246,7 +246,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.10 2000/09/29 20:21:34 pet
    
     
      Overall backend code speed has been increased by approximately 20-40%, 
-     and backend start-up time has decreased 80% since v6.0 was released.
+     and backend start-up time has decreased 80% since version 6.0 was released.
     
    
   

diff --git a/doc/src/sgml/jdbc.sgml b/doc/src/sgml/jdbc.sgml
index fb00aa829ea6333c46c7316de5f6257a3f030aa5..575087fd955a7b150bf7f18dd7457f7778098b15 100644 (file)
--- a/doc/src/sgml/jdbc.sgml
+++ b/doc/src/sgml/jdbc.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -438,7 +438,7 @@ db.close();
       For Postgres, you must access large
       objects within an SQL transaction. Although this has always been 
       true in principle, it was not strictly enforced until the
-      release of v6.5. You would open a transaction by using the
+      release of version 6.5. You would open a transaction by using the
       setAutoCommit() method with an input
       parameter of false:
 
@@ -2642,7 +2642,7 @@ Both are available on
 
 My own web site
  contains updated information not included in this 
-document, and also includes precompiled drivers for v6.4, and earlier.
+document, and also includes precompiled drivers for versions 6.4 and earlier.
 
 
 

diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml
index 43daa3c12c3cb1f85721132cde9fb8ff8cd3a458..9d25be88fd9a73bf80b34dad06edec4140cec609 100644 (file)
--- a/doc/src/sgml/lobj.sgml
+++ b/doc/src/sgml/lobj.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -70,7 +70,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.13 2000/09/29 20:21:34 petere
      
       All large object manipulation must take
       place within an SQL transaction. This requirement is strictly
-      enforced as of Postgres v6.5, though it has been an
+      enforced as of Postgres 6.5, though it has been an
       implicit requirement in previous versions, resulting in
       misbehavior if ignored.
      

diff --git a/doc/src/sgml/notation.sgml b/doc/src/sgml/notation.sgml
index 4d978b5131765049ae6b1dffad502994dc8a8458..f7991aba17b95637d8371dd7d385f4a6cf9dbc0e 100644 (file)
--- a/doc/src/sgml/notation.sgml
+++ b/doc/src/sgml/notation.sgml
@@ -1,5 +1,5 @@
 
 
 
@@ -109,7 +109,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.10 2000/05/02 20:01:52 th
 
  
   
-   At the time of writing (Postgres v7.0)
+   At the time of writing (Postgres 7.0)
    the notation for
    flagging commands is not universally consistant throughout the
    documentation set.

diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index 8be998bb50f01a8678df20acf2e85b53ed0ca6d9..bcf3399ebcc11610cdc0f8e4a957f18053105489 100644 (file)
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -20,7 +20,7 @@ Updates for protocol 2.0 by Tom Lane
 
 Postgres uses a message-based protocol for communication between frontends
 and backends.  The protocol is implemented over TCP/IP and also on Unix sockets.
-Postgres v6.3 introduced version numbers into the protocol.
+Postgres 6.3 introduced version numbers into the protocol.
 This was done in such
 a way as to still allow connections from earlier versions of frontends, but
 this document does not cover the protocol used by those earlier versions.
@@ -28,7 +28,7 @@ this document does not cover the protocol used by those earlier versions.
 
 
 This document describes version 2.0 of the protocol, implemented in
-Postgres v6.4 and later.
+Postgres 6.4 and later.
 
 
 

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index bd33d88129974288fbf776ca80434fcf6c208d03..adb1243510158f9b9f34def124aedfdab9f25e5a 100644 (file)
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -106,7 +106,7 @@ Subqueries in FROM are now supported.
    
 
    
-    Migration to v7.1
+    Migration to v<span class="marked">ersion </span>7.1
 
     
    A dump/restore using pg_dump is required for those wishing to migrate
@@ -306,11 +306,11 @@ New template0 database that contains no user additions(Tom)
 
 
    
-    Migration to v7.0.3
+    Migration to v<span class="marked">ersion </span>7.0.3
 
     
      A dump/restore is not required for those running
-     v7.0.*.
+     7.0.*.
     
    
 
@@ -384,11 +384,11 @@ Fix for crash of backend, on abort (Tom)
 
 
    
-    Migration to v7.0.2
+    Migration to v<span class="marked">ersion </span>7.0.2
 
     
      A dump/restore is not required for those running
-     v7.*.
+     7.*.
     
    
 
@@ -424,11 +424,11 @@ Added documentation to tarball.
    
 
    
-    Migration to v7.0.1
+    Migration to v<span class="marked">ersion </span>7.0.1
 
     
      A dump/restore is not required for those running
-     v7.0.
+     7.0.
     
    
 
@@ -561,7 +561,7 @@ ecpg changes (Michael)
    
 
    
-    Migration to v7.0
+    Migration to v<span class="marked">ersion </span>7.0
 
     
      A dump/restore using pg_dump
@@ -987,7 +987,7 @@ New multibyte encodings
 
 
    
-    Migration to v6.5.3
+    Migration to v<span class="marked">ersion </span>6.5.3
 
     
      A dump/restore is not required for those running
@@ -1030,7 +1030,7 @@ Fix dumping rules on inherited tables
 
 
    
-    Migration to v6.5.2
+    Migration to v<span class="marked">ersion </span>6.5.2
 
     
      A dump/restore is not required for those running
@@ -1095,7 +1095,7 @@ Updated version of pgaccess 0.98
    
 
    
-    Migration to v6.5.1
+    Migration to v<span class="marked">ersion </span>6.5.1
 
     
      A dump/restore is not required for those running
@@ -1299,7 +1299,7 @@ Add Win1250 (Czech) support (Pavel Behal)
    
 
    
-    Migration to v6.5
+    Migration to v<span class="marked">ersion </span>6.5
 
     
      A dump/restore using pg_dump
@@ -1565,7 +1565,7 @@ bug fix.
 
 
 
-Migration to v6.4.2
+Migration to v<span class="marked">ersion </span>6.4.2
 
 
 A dump/restore is not required for those running
@@ -1609,7 +1609,7 @@ problems reported by 6.4 users.
 
 
 
-Migration to v6.4.1
+Migration to v<span class="marked">ersion </span>6.4.1
 
 
 A dump/restore is not required for those running
@@ -1752,7 +1752,7 @@ been.
 
 
 
-Migration to v6.4
+Migration to v<span class="marked">ersion </span>6.4
 
 
 A dump/restore using pg_dump 
@@ -1983,7 +1983,7 @@ new Makefile.shlib for shared library configuration(Tom)
 
 
 This is a bugfix release for 6.3.x.
-Refer to the release notes for v6.3 for a more complete summary of new features.
+Refer to the release notes for version 6.3 for a more complete summary of new features.
 
 
 Summary:
@@ -1992,7 +1992,7 @@ Summary:
 
 
 Repairs automatic configuration support for some platforms, including Linux,
-from breakage inadvertently introduced in v6.3.1.
+from breakage inadvertently introduced in version 6.3.1.
 
 
 
@@ -2011,8 +2011,8 @@ This last step should be performed while the postmaster is not running.
 You should re-link any custom applications that use Postgres libraries.
 
 
-For upgrades from pre-v6.3 installations,
-refer to the installation and migration instructions for v6.3.
+For upgrades from pre-6.3 installations,
+refer to the installation and migration instructions for version 6.3.
 
 
    
@@ -2095,8 +2095,8 @@ This last step should be performed while the postmaster is not running.
 You should re-link any custom applications that use Postgres libraries.
 
 
-For upgrades from pre-v6.3 installations,
-refer to the installation and migration instructions for v6.3.
+For upgrades from pre-6.3 installations,
+refer to the installation and migration instructions for version 6.3.
 
 
    
@@ -2271,7 +2271,7 @@ Better identify tcl and tk libs and includes(Bruce)
    
 
    
-    Migration to v6.3
+    Migration to v<span class="marked">ersion </span>6.3
 
     
      A dump/restore using pg_dump 
@@ -2473,7 +2473,7 @@ Remove un-needed malloc() calls and replace with palloc()(Bruce)
 1997-10-17
 
 
-v6.2.1 is a bug-fix and usability release on v6.2.
+6.2.1 is a bug-fix and usability release on 6.2.
 
 
 Summary:
@@ -2494,20 +2494,20 @@ Include example trigger function for inserting user names on table updates.
 
 
 
-This is a minor bug-fix release on v6.2. 
-For upgrades from pre-v6.2 systems, a full dump/reload is required. 
-Refer to the v6.2 release notes for instructions.
+This is a minor bug-fix release on 6.2. 
+For upgrades from pre-6.2 systems, a full dump/reload is required. 
+Refer to the 6.2 release notes for instructions.
 
 
 
-Migration from v<span class="marked">6.2 to v</span>6.2.1
+Migration from v<span class="marked">ersion 6.2 to version </span>6.2.1
 
 
-This is a minor bug-fix release. A dump/reload is not required from v6.2,
-but is required from any release prior to v6.2.
+This is a minor bug-fix release. A dump/reload is not required from version 6.2,
+but is required from any release prior to 6.2.
 
 
-In upgrading from v6.2, if you choose to dump/reload you will find that
+In upgrading from version 6.2, if you choose to dump/reload you will find that
 avg(money) is now calculated correctly. All other bug fixes take effect
 upon updating the executables.
 
@@ -2570,7 +2570,7 @@ previous releases of Postgres.
 
 
 
-Migration from v<span class="marked">6.1 to v</span>6.2
+Migration from v<span class="marked">ersion 6.1 to version </span>6.2
 
 
 This migration requires a complete dump of the 6.1 database and a
@@ -2583,7 +2583,7 @@ to dump the 6.1 database.
 
 
 
-Migration from v<span class="marked">1.x to v</span>6.2
+Migration from v<span class="marked">ersion 1.<replaceable>x</> to version </span>6.2
 
 
 Those migrating from earlier 1.* releases should first upgrade to 1.09
@@ -2725,15 +2725,15 @@ SPI and Trigger programming guides (Vadim & D'Arcy)
 
 
 
-Migration from v<span class="marked">6.1 to v</span>6.1.1
+Migration from v<span class="marked">ersion 6.1 to version </span>6.1.1
 
 
 1997-07-22
 
 
-This is a minor bug-fix release. A dump/reload is not required from v6.1,
-but is required from any release prior to v6.1.
-Refer to the release notes for v6.1 for more details.
+This is a minor bug-fix release. A dump/reload is not required from version 6.1,
+but is required from any release prior to 6.1.
+Refer to the release notes for 6.1 for more details.
 
 
 
@@ -2783,7 +2783,7 @@ pg_dumpall now returns proper status, portability fix(Bruce)
 
 
   The regression tests have been adapted and extensively modified for the
-  v6.1 release of Postgres.
+  6.1 release of Postgres.
 
 
 
@@ -2795,7 +2795,7 @@ pg_dumpall now returns proper status, portability fix(Bruce)
 
 
 
-  Postgres v6.1 introduces a new, alternate
+  Postgres 6.1 introduces a new, alternate
 optimizer which uses genetic
   algorithms. These algorithms introduce a random behavior in the ordering
   of query results when the query contains multiple qualifiers or multiple
@@ -2828,7 +2828,7 @@ optimizer which uses genetic
 
 
 
-Migration to v6.1
+Migration to v<span class="marked">ersion </span>6.1
 
 
 This migration requires a complete dump of the 6.0 database and a
@@ -2945,7 +2945,7 @@ DG-UX, Ultrix, Irix, AIX portability fixes
 
 
 
-Release <span class="marked">v</span>6.0
+Release 6.0
 
 
 
-Migration from v<span class="marked">1.02 to v</span>1.02.1
+Migration from v<span class="marked">ersion 1.02 to version </span>1.02.1
 
 
 1996-08-01
@@ -3281,7 +3281,7 @@ Contributors (appologies to any missed)
 
 
 
-Release <span class="marked">v</span>1.01
+Release 1.01
 
 
 
-Migration from v<span class="marked">1.0 to v</span>1.01
+Migration from v<span class="marked">ersion 1.0 to version </span>1.01
 
 
 1996-02-23
@@ -3481,7 +3481,7 @@ Bug fixes:
 
 
 
-Release <span class="marked">v</span>1.0
+Release 1.0
 
 
  
@@ -184,8 +184,7 @@ DATETIME TIMESPAN
 
      (translated to TIMESTAMP and INTERVAL,
      respectively). This feature is intended to help with
-     transitioning to v7.0, and will be removed in the next full
-     release (likely v7.1).
+     transitioning to version 7.0, and will be removed in a future release.
     
 
     
@@ -193,7 +192,7 @@ DATETIME TIMESPAN
      or SQL3 reserved key words
      which are not key words in Postgres.
      These have no proscribed usage in Postgres
-     at the time of writing (v7.0) but may become reserved key words in the
+     at the time of writing (version 7.0) but may become reserved key words in the
      future:
 
      

diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml
index f2dc29817460700a7a9006fd1e0f5c4ede7a156d..5d192cc4ed34404485a68106e4fef98fdb46583b 100644 (file)
--- a/doc/src/sgml/xfunc.sgml
+++ b/doc/src/sgml/xfunc.sgml
@@ -1,5 +1,5 @@
 
 
  
@@ -1226,7 +1226,7 @@ LANGUAGE 'c';
     Name Space Conflicts
 
     
-     As of Postgres v7.0, the alternative
+     As of Postgres 7.0, the alternative
      form of the AS clause for the SQL
      CREATE FUNCTION command
      decouples the SQL function name from the function name in the C
@@ -1235,7 +1235,7 @@ LANGUAGE 'c';
     
 
     
-     Pre-<span class="marked">v</span>7.0
+     Pre-7.0
 
      
       For functions written in C, the SQL name declared in