o they sometimes returns a result garbage string appended.
    o they do not work if client encoding is different from server
      encoding

Overall a really nice job here, Peter ...

the interactive docs.

enforce a limit on who can connect to databases other than their own.
From a recent discussion in pg-admin.

StÅphane Raimbault.

escape character.

encodings.

copy editing.

GiST does now, too.  (Someone needs to write a description of GiST
to add to this chapter.  I don't know enough about it ...)

Admin Guide.  Move discussion of template databases out of footnotes
in CREATE DATABASE ref page and into a section of the Admin Guide.
Clean up various obsolete claims, do some copy-editing.

Place it in the expected place in the User's Guide, rather than
hiding it in the command reference page for CREATE SEQUENCE.

search lists was broken in such a way that only the most recent
instance of a given hash code would ever be searched, thus possibly
missing longer matches further back.  Fixing this gave 5 to 10%
compression improvement on some text test cases.  Additional small
tweaks to improve speed of inner loops a little bit.  There is no
compatibility issue created by this change, since the compressed data
format and decompression algorithm don't change.

This seems the right thing for most usages, but I notice two places
where it is the wrong thing.  One is that the default permissions on
TOAST rels should be no-access, not world-readable; the other is that
PrepareForTupleInvalidation doesn't really need to spend time looking
at tuples of TOAST relations.

Kevin Jacobs and Brad McLean.

and comment in src/backend/parser/Makefile for the technical details.

discussions in pghackers.

mutually exclusive keyword lists spanning all known keywords ---
including AS.  Moved COALESCE and a few other ColLabels into the
can-be-ColId list.