problems are indeed fixed.

the case wherein zero was rejected for a field like NUMERIC(4,4).
Miscellaneous other code beautification efforts.

functions, which would lead to trouble with datatypes that paid attention
to the typelem or typmod parameters to these functions.  In particular,
incorrect code in pg_aggregate.c explains the platform-specific failures
that have been reported in NUMERIC avg().

regress test expected outputs were committed with NOTICEs appearing out
of order.  Update to correct results.

work now that did not work in 6.5.

- Prevent permissions on indexes
- Instituted --enable-multibyte option and tweaked the MB build process where necessary
- initdb prompts for superuser password

* Let unprivileged users change their own passwords.

* The password is now an Sconst in the parser, which better reflects its text datatype and also
forces users to quote them.

* If your password is NULL you won't be written to the password file, meaning you can't connect
until you have a password set up (if you use password authentication).

* When you drop a user that owns a database you get an error. The database is not gone.

in libpq --- mostly, poor response to error conditions.  You now actually
get to see the postmaster's 'The Data Base System is starting up' message,
which you didn't before.  I suspect the SSL code is still broken though.

report original error before attempting reset, not after.

80-column displays...

choke on relation or attribute names containing spaces, quotes, or other
special characters.  This fixes a TODO item.  It also forces initdb,
since stored rule strings change.

error-proof. Rearranged some old code and removed dead sections.

Update README so that it reflects all source file names
Add an entry to make sjistest (testing between SJIS/EUC_JP conversion)

on FUNC_MAX_ARGS by using an appropriate fmgr() call.