'make install'; there are enough of 'em that this slowed down the make
noticeably.  Ensure that 'all' is the default make target in all these
directories (defaulting to 'make install' is surprising and dangerous
IMHO).  Fix a couple small typos.

usually anyway.

> * Gavin Sherry <swm@linuxworld.com.au>

case for timestamptz input, and differently wrong answers in the float-
timestamp case for timestamp input.

creation to world, but disallow temp table creation in template1.  Per
latest round of pghackers discussion.
I did not force initdb, but the permissions lockdown on template1 will
not take effect unless you do one (or manually REVOKE TEMP ON DATABASE template1 FROM public).

somewhat less likely to provoke a conflict.

referring to "multibyte" where it really means character encoding.

a series of localtime() calls to determine the local timezone offset
when mktime() fails.  This eliminates regression failures on RHL 7.3,
and should continue to work until it occurs to the glibc boys to break
localtime() as well.  By then I hope we'll have our own timezone code...

convert date to tm' failures, by using DetermineLocalTimeZone() instead.

(INT64_FORMAT), which gettext cannot handle.

> * to_char(0,'FM999.99') returns a period, to_char(1,'FM999.99') does not

heap, not just ExclusiveLock.

< 	o -ALTER TABLE ADD PRIMARY KEY (Christopher)
< 	o -ALTER TABLE ADD UNIQUE (Christopher)
> 	o -ALTER TABLE ADD PRIMARY KEY (Tom)
> 	o -ALTER TABLE ADD UNIQUE (Tom)

seems we have a choice between annoying messages and leaking memory
(or dumping core, but that's right out).  Patch also fixes several
other problems in pg_disconnect, such as being willing to close a
channel that isn't a PG channel.

Gerhard Hintermayer, revised and documented by Tom Lane.

This patch also fixes a 'must fix' bug: libpgtcl's LISTEN/NOTIFY
support was broken by the recent changes to the PGnotify structure.
Guess that change wasn't quite so safe as we thought.

more flexible, and improve the error reporting.  Also, add documentation
for REPLACE RULE/VIEW.

< 	o -ALTER TABLE ALTER COLUMN SET/DROP NOT NULL (Christopher Kings-Lynne)
< 	o ALTER TABLE ADD COLUMN column SERIAL doesn't create sequence
> 	o -ALTER TABLE ALTER COLUMN SET/DROP NOT NULL (Christopher)
200a200,201
> 	o ALTER TABLE ADD COLUMN column SERIAL doesn't create sequence because
>           of the item above
232c233
< 	o -Disallow missing columns in INSERT ... VALUES, per ANSI
> 	o -Disallow missing columns in INSERT ... (col) VALUES, per ANSI
335,336d335
< * Have SERIAL generate non-colliding sequence names when we have
<   auto-destruction