(Thanks to Bruce for finding what caused problem).

 rather than assuming FALSE).

 CURRENT_USER.
Add syntax for primary and foreign keys.
Change optional syntax in CREATE INDEX to avoid parsing conflict with
 TIMESTAMP WITH TIME ZONE data type (use USING <class> rather than WITH...).
Decouple various categories of data type syntax to allow the most possible
 non-ambiguous extensions to SQL92 for column names and labels. This should
 make the parser a bit more understandable, or at least easier to find
 where and how the data types are handled.
Support syntax for IN and EXISTS clauses with subselects.
Support SQL92 syntax for IS TRUE/IS FALSE/IS NOT TRUE/IS NOT FALSE.

Add keywords for national character types.
Shorted date/time keyword token names for convenience.
Add SQL3 reserved words TRUE and FALSE.

Change a few routine names to ensure <= 16 characters in name
 to fit correctly into pg_proc.

 from "action" to "ev_action".

 to "ev_action".

to changes in parser.

Shorten a few routine names to <= 16 characters long to fit in table.

 in DecodeTimeOnly(). Only present when seconds are not specified
 for input.

Rename date+time conversion to datetime to ensure less than 16 characters
 in routine name (required to fit in pg_proc table).

Before, char16 was missing last character for output.

Allow true/false, yes/no, 1/0. Throw elog warning if anything else.
Allow shorter strings, so "t", "tr", "tru" and "true" match "true".
Old behavior accepted anything starting with "t" as TRUE,
 everything else as FALSE.

Should have been here in time for 6.2.1 release...

Install compiled functions into $(LIBDIR)/contrib.
(Thanks to Brook Milligan <brook@trillium.NMSU.Edu>)

Leave all other input values to return FALSE.
In next version, do more checking for valid inputs for both TRUE and FALSE.