Commit b2145e93 authored by Peter Eisentraut's avatar Peter Eisentraut

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

full word "version" where appropriate.
parent 8f89113d
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.10 2000/09/29 20:21:33 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.11 2000/12/21 22:55:26 petere Exp $
--> -->
<chapter id="overview"> <chapter id="overview">
...@@ -1724,7 +1724,7 @@ havingQual} to the one attached to the field {\tt havingQual} of the ...@@ -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 {\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 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 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} \begin{verbatim}
void void
...@@ -1752,7 +1752,7 @@ existing until v6.3.2. It has been created for the {\it having logic}. ...@@ -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 This function is similar to the above described function {\tt
AddHavingQual()}. It also adds the {\it operator tree} given by the AddHavingQual()}. It also adds the {\it operator tree} given by the
parameter {\tt havingQual} but prefixes it by a {\tt NOT} node. {\tt 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}. created for the {\it having logic}.
% %
\begin{verbatim} \begin{verbatim}
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.10 2000/09/29 20:21:33 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.11 2000/12/21 22:55:26 petere Exp $
CVS code repository CVS code repository
Thomas Lockhart Thomas Lockhart
--> -->
...@@ -99,7 +99,7 @@ $ cvs checkout -r REL6_4 tc ...@@ -99,7 +99,7 @@ $ cvs checkout -r REL6_4 tc
</para> </para>
<para> <para>
So, to create the v6.4 release So, to create the 6.4 release
I did the following: I did the following:
<programlisting> <programlisting>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.13 2000/10/20 13:57:10 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.14 2000/12/21 22:55:27 petere Exp $
Date/time details Date/time details
--> -->
...@@ -622,7 +622,7 @@ Date/time details ...@@ -622,7 +622,7 @@ Date/time details
Gregorian years 1-99AD may be entered by using 4 digits with leading Gregorian years 1-99AD may be entered by using 4 digits with leading
zeros (e.g. 0099 is 99AD). Previous versions of zeros (e.g. 0099 is 99AD). Previous versions of
<productname>Postgres</productname> accepted years with three <productname>Postgres</productname> 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. been tightened up to reduce the possibility of ambiguity.
</para> </para>
</tip> </tip>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.10 2000/09/29 20:21:34 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.11 2000/12/21 22:55:27 petere Exp $
--> -->
<sect1 id="history"> <sect1 id="history">
...@@ -246,7 +246,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.10 2000/09/29 20:21:34 pet ...@@ -246,7 +246,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.10 2000/09/29 20:21:34 pet
<listitem> <listitem>
<para> <para>
Overall backend code speed has been increased by approximately 20-40%, 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.
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.15 2000/10/27 22:28:23 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.16 2000/12/21 22:55:27 petere Exp $
--> -->
<chapter id="jdbc"> <chapter id="jdbc">
...@@ -438,7 +438,7 @@ db.close(); ...@@ -438,7 +438,7 @@ db.close();
For <productname>Postgres</productname>, you must access large For <productname>Postgres</productname>, you must access large
objects within an SQL transaction. Although this has always been objects within an SQL transaction. Although this has always been
true in principle, it was not strictly enforced until the 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
<function>setAutoCommit()</function> method with an input <function>setAutoCommit()</function> method with an input
parameter of <literal>false</literal>: parameter of <literal>false</literal>:
...@@ -2642,7 +2642,7 @@ Both are available on ...@@ -2642,7 +2642,7 @@ Both are available on
<para> <para>
<ulink url="http://www.retep.org.uk">My own web site</ulink> <ulink url="http://www.retep.org.uk">My own web site</ulink>
contains updated information not included in this 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.
</para> </para>
</sect1> </sect1>
</chapter> </chapter>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.13 2000/09/29 20:21:34 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.14 2000/12/21 22:55:27 petere Exp $
--> -->
<chapter id="largeObjects"> <chapter id="largeObjects">
...@@ -70,7 +70,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.13 2000/09/29 20:21:34 petere ...@@ -70,7 +70,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.13 2000/09/29 20:21:34 petere
<para> <para>
All large object manipulation <emphasis>must</emphasis> take All large object manipulation <emphasis>must</emphasis> take
place within an SQL transaction. This requirement is strictly 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 implicit requirement in previous versions, resulting in
misbehavior if ignored. misbehavior if ignored.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.10 2000/05/02 20:01:52 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.11 2000/12/21 22:55:27 petere Exp $
--> -->
<sect1 id="terminology"> <sect1 id="terminology">
...@@ -109,7 +109,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.10 2000/05/02 20:01:52 th ...@@ -109,7 +109,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.10 2000/05/02 20:01:52 th
<note> <note>
<para> <para>
At the time of writing (<Productname>Postgres</Productname> v7.0) At the time of writing (<Productname>Postgres</Productname> 7.0)
the notation for the notation for
flagging commands is not universally consistant throughout the flagging commands is not universally consistant throughout the
documentation set. documentation set.
......
...@@ -20,7 +20,7 @@ Updates for protocol 2.0 by <ULink url="mailto:tgl@sss.pgh.pa.us">Tom Lane</ULin ...@@ -20,7 +20,7 @@ Updates for protocol 2.0 by <ULink url="mailto:tgl@sss.pgh.pa.us">Tom Lane</ULin
<Para> <Para>
<ProductName>Postgres</ProductName> uses a message-based protocol for communication between frontends <ProductName>Postgres</ProductName> uses a message-based protocol for communication between frontends
and backends. The protocol is implemented over <Acronym>TCP/IP</Acronym> and also on Unix sockets. and backends. The protocol is implemented over <Acronym>TCP/IP</Acronym> and also on Unix sockets.
<ProductName>Postgres</ProductName> v6.3 introduced version numbers into the protocol. <ProductName>Postgres</ProductName> 6.3 introduced version numbers into the protocol.
This was done in such This was done in such
a way as to still allow connections from earlier versions of frontends, but 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. 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. ...@@ -28,7 +28,7 @@ this document does not cover the protocol used by those earlier versions.
<Para> <Para>
This document describes version 2.0 of the protocol, implemented in This document describes version 2.0 of the protocol, implemented in
<ProductName>Postgres</ProductName> v6.4 and later. <ProductName>Postgres</ProductName> 6.4 and later.
</para> </para>
<Para> <Para>
......
This diff is collapsed.
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.29 2000/12/18 23:39:37 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.30 2000/12/21 22:55:27 petere Exp $
--> -->
<chapter id="syntax"> <chapter id="syntax">
...@@ -184,8 +184,7 @@ DATETIME TIMESPAN ...@@ -184,8 +184,7 @@ DATETIME TIMESPAN
(translated to <type>TIMESTAMP</type> and <type>INTERVAL</type>, (translated to <type>TIMESTAMP</type> and <type>INTERVAL</type>,
respectively). This feature is intended to help with respectively). This feature is intended to help with
transitioning to v7.0, and will be removed in the next full transitioning to version 7.0, and will be removed in a future release.
release (likely v7.1).
</para> </para>
<para> <para>
...@@ -193,7 +192,7 @@ DATETIME TIMESPAN ...@@ -193,7 +192,7 @@ DATETIME TIMESPAN
or <acronym>SQL3</acronym> reserved key words or <acronym>SQL3</acronym> reserved key words
which are not key words in <productname>Postgres</productname>. which are not key words in <productname>Postgres</productname>.
These have no proscribed usage in <productname>Postgres</productname> These have no proscribed usage in <productname>Postgres</productname>
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: future:
<note> <note>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/xfunc.sgml,v 1.23 2000/11/20 20:36:47 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/xfunc.sgml,v 1.24 2000/12/21 22:55:27 petere Exp $
--> -->
<chapter id="xfunc"> <chapter id="xfunc">
...@@ -1226,7 +1226,7 @@ LANGUAGE 'c'; ...@@ -1226,7 +1226,7 @@ LANGUAGE 'c';
<title>Name Space Conflicts</title> <title>Name Space Conflicts</title>
<para> <para>
As of <productname>Postgres</productname> v7.0, the alternative As of <productname>Postgres</productname> 7.0, the alternative
form of the AS clause for the SQL form of the AS clause for the SQL
<command>CREATE FUNCTION</command> command <command>CREATE FUNCTION</command> command
decouples the SQL function name from the function name in the C decouples the SQL function name from the function name in the C
...@@ -1235,7 +1235,7 @@ LANGUAGE 'c'; ...@@ -1235,7 +1235,7 @@ LANGUAGE 'c';
</para> </para>
<sect3> <sect3>
<title>Pre-v7.0</title> <title>Pre-7.0</title>
<para> <para>
For functions written in C, the SQL name declared in For functions written in C, the SQL name declared in
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment