now that sequence names are properly quoted for field defaults, mixed
case sequence names are generated. These are properly quoted in the
CREATE SEQUENCE lines, but not in the SELECT nextval lines, as per
below:

CREATE SEQUENCE "Teams_TeamID_seq" start 10 increment 1 maxvalue
2147483647 minvalue 1  cache 1 ;
SELECT nextval ('Teams_TeamID_seq');

This needs to be:
SELECT nextval ('"Teams_TeamID_seq"');

Patch included below.
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>

This is because (-1) << 32 is -1 (Only intel arc. has been checked)

Oleg Sharoiko

 for v6.5.2 info.

arbitrarily long strings, and frontends should cope gracefully.  Goes
along with long query and long error message changes...

 Thanks to Michael Deck <deckm@cleansoft.com> for the tipoff.
Add more examples for language components.

and fix_opids processing to a single recursive pass over the plan tree
executed at the very tail end of planning, rather than haphazardly here
and there at different places.  Now that tlist Vars do not get modified
until the very end, it's possible to get rid of the klugy var_equal and
match_varid partial-matching routines, and just use plain equal()
throughout the optimizer.  This is a step towards allowing merge and
hash joins to be done on expressions instead of only Vars ...

and
for src/data directories, and one minor patch for doc/README.locale.
   Please apply.

Oleg.