Hello,
Here is a patch for some doubled words in the manual
(e.g. "the the").
I'm in the process of producing a printed version of
the documentation in book format. If anyone from the
PostgreSQL team would like to see the proofs before
they go to press I'll be glad to make them available.
--
best regards,
Brian Gough
Network Theory Ltd,
Publishing Free Software Manuals --- http://www.network-theory.co.uk/
Index: doc/src/sgml/datatype.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/datatype.sgml,v
retrieving revision 1.198
diff -u -r1.198 datatype.sgml
--- doc/src/sgml/datatype.sgml 21 Apr 2007 17:26:17 -0000 1.198
+++ doc/src/sgml/datatype.sgml 3 May 2007 13:57:46 -0000
@@ -3376,7 +3376,7 @@
<para>
When using the binary mode to pass query parameters to the server
- and query results back the the client, no character set conversion
+ and query results back to the client, no character set conversion
is performed, so the situation is different. In this case, an
encoding declaration in the XML data will be observed, and if it
is absent, the data will be assumed to be in UTF-8 (as required by
Index: doc/src/sgml/ddl.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ddl.sgml,v
retrieving revision 1.73
diff -u -r1.73 ddl.sgml
--- doc/src/sgml/ddl.sgml 1 Feb 2007 00:28:16 -0000 1.73
+++ doc/src/sgml/ddl.sgml 3 May 2007 13:57:48 -0000
@@ -2233,7 +2233,7 @@
<listitem>
<para>
- When queries or updates access a large percentage of a a single
+ When queries or updates access a large percentage of a single
partition, performance can be improved by taking advantage
of sequential scan of that partition instead of using an
index and random access reads scattered across the whole table.
@@ -2556,7 +2556,7 @@
</programlisting>
Note that the <literal>WHERE</literal> clause in each rule
- exactly matches the the <literal>CHECK</literal>
+ exactly matches the <literal>CHECK</literal>
constraint for its partition.
</para>
</listitem>
Index: doc/src/sgml/plperl.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/plperl.sgml,v
retrieving revision 2.64
diff -u -r2.64 plperl.sgml
--- doc/src/sgml/plperl.sgml 16 Feb 2007 03:50:29 -0000 2.64
+++ doc/src/sgml/plperl.sgml 3 May 2007 13:57:52 -0000
@@ -20,7 +20,7 @@
<para> The usual advantage to using PL/Perl is that this allows use,
within stored functions, of the manyfold <quote>string
munging</quote> operators and functions available for Perl. Parsing
- complex strings might be be easier using Perl than it is with the
+ complex strings might be easier using Perl than it is with the
string functions and control structures provided in PL/pgSQL.</para>
<para>
@@ -619,7 +619,7 @@
$$ LANGUAGE plperl;
</programlisting>
The creation of this function will fail as its use of a forbidden
- operation will be be caught by the validator.
+ operation will be caught by the validator.
</para>
<para>
Index: doc/src/sgml/spi.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/spi.sgml,v
retrieving revision 1.56
diff -u -r1.56 spi.sgml
--- doc/src/sgml/spi.sgml 16 Apr 2007 01:14:55 -0000 1.56
+++ doc/src/sgml/spi.sgml 3 May 2007 13:57:54 -0000
@@ -2233,7 +2233,7 @@
Column value, or <symbol>NULL</symbol> if the column is null,
<parameter>colnumber</parameter> is out of range
(<varname>SPI_result</varname> is set to
- <symbol>SPI_ERROR_NOATTRIBUTE</symbol>), or no no output function
+ <symbol>SPI_ERROR_NOATTRIBUTE</symbol>), or no output function is
available (<varname>SPI_result</varname> is set to
<symbol>SPI_ERROR_NOOUTFUNC</symbol>).
</para>