Add some chapters on new topics.
Change to referencing OASIS/Docbook v3.1 rather than Davenport/Docbook v3.0
Grepped for and fixed apparent tag mangling from emacs
 "Normalize" operation. Should be the last of those.

Add PL/perl docs from Mark Hollomon.
Put language-specific docs into the User's Guide, and move the rest
 to the Programmer's Guide.

newer Alpha platforms.

broken almost since the word go ... I guess no one ever ran it ...

 single integers, and lists of names, without surrounding them with quotes.
Remove all tokens which are defined as operators from ColID and ColLabel
 to avoid precedence confusion. Thanks to Tom Lane for catching this.

to use -g ... especially not when this can cause real problems on some
platforms ...

from Bill.Allie@mug.org.

inclusions of system headers more consistent.

'#include <string>' work in the local C++ compiler.

 Programmer's Guide does not have access to the reference page.
Normalize markup.

to next integer.  Previously, if selectivity was small, we could compute
very tiny scan cost on the basis of estimating that only 0.001 tuple
would be fetched, which is silly.  This naturally led to some rather
silly plans...

 years. Rejects dates like '0.085', which were accepted previously.

 years. Rejects dates like '0.085', which were accepted previously.
Minor mods of ODBC markup.

Update porting info. Still need a lot of platforms tested.
Fix small errors in markup.

Matches postgresql.org/hub.org environment.

class.  This chapter was apparently sewed together from several
inconsistent examples... and perhaps from old docs that no longer
apply at all.

Use "generic functions" for math and other routines.
Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".

Move CREATE FUNCTION/WITH clause to end of statement to get around
 shift/reduce conflicts with type names containing "WITH".
Add lots of tokens as allowed ColId's and/or ColLabel's,
 so this should be a complete set for the v7.0 release.

We still have an internal limit in the ODBC code of 8 columns per key,
 but this should lay the groundwork for resolving that.
Includes reformulated query from Tom Lane.