the relevant fixes to 8.2 as well.
<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.
</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>
<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 may be be easier using Perl than it is with the
+ complex strings may be easier using Perl than it is with the
string functions and control structures provided in PL/pgSQL.</para>
<para>
$$ 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>
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>