compatibility library which contains a 'main' function, which is not good.
If someone really needed it, think of a different plan.

Improve documentation, too.

Remove timestamps from messages where this would be redundant with the
log_timestamp option.

documentation.

rather than just being aliases for int4in/int4out.  Give type Oid a
full set of comparison operators that do proper unsigned comparison,
instead of reusing the int4 comparators.  Since pg_dump is now doing
unsigned comparisons of OIDs, it is now *necessary* that we play by
the rules here.  In fact, given that btoidcmp() has been doing unsigned
comparison for quite some time, it seems likely that we have index-
corruption problems in 7.0 and before once the Oid counter goes past
2G.  Fixing these operators is a necessary step before we can think
about 8-byte Oid, too.

(should fix OID bootstraping).

new separate relkind for views (per some discussion back in September).
I didn't force initdb, but rules regress test will show differences
until you do one.

per bug report from Don Baccus.

Thanks to Martin A. Marques <martin@math.unl.edu.ar> for the tip.

in pghackers list.  Support for oldstyle internal functions is gone
(no longer needed, since conversion is complete) and pg_language entry
'internal' now implies newstyle call convention.  pg_language entry
'newC' is gone; both old and newstyle dynamically loaded C functions
are now called language 'C'.  A newstyle function must be identified
by an associated info routine.  See src/backend/utils/fmgr/README.

'long long int' portions of ecpg if the type or these functions don't
exist.

of user-defined functions (forget 'C' vs 'newC', instead require an info
function to be present for new-style functions).  Also update some other
out-of-date commentary.

option conventions.  (E.g., "pg_passwd -?" should not write to a file named
"-?".)