Fixed.
---------------------------------------------------------------------------
Bruno Wolff III wrote:
> On Mon, Aug 22, 2005 at 23:16:14 -0400,
> Bruce Momjian <pgman@candle.pha.pa.us> wrote:
> > I have compiled the 8.1 release notes and converted them to SGML at:
> >
> > http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
> >
> > I still need to add markup and cleanup, but it is good enough for
> > review and for beta1. I will work on it more tomorrow.
>
> I spotted a couple of typos:
>
> I think that 'not' should be 'now' in the following:
> In previous releases, the only way to use index for MIN/MAX was to rewrite the query as SELECT col FROM tab ORDER BY
colLIMIT 1. This not happens automatically.
>
> I think that 'of' should be 'off' in the following:
> To prevent partial disk writes from corrupting the database, PostgreSQL writes a complete copy of each database disk
pageto WAL the first time it is modified after a checkpoint. This turns of that functionality for users with
battery-backeddisk caches where partial page writes can not happen.
>
> I don't think you want a double negative ('not' and 'INconsistant') in the
> following:
> In release 8.0, carriage returns and line feeds in CSV COPY TO were not processed in a inconsitent manner. (This was
documentedon the TODO list.)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073