existing code of dbname optional actually work.

< * Change 'createlang [langname] dbname' to 'createlang langname [dbname]'

> * Change 'createlang [langname] dbname' to 'createlang langname [dbname]'

per bug report from Laurette Cisneros.

formats will be taken as 2000, not year zero.  Per bug report from
Aasmund Midttun Godal.  Fix from Karel Zak.

(IMHO) the code should be fixed to do what the documentation formerly
claimed, and then revert this change.

macros, but only at explicit CHECK_FOR_INTERRUPTS() calls.  Not clear
whether overenthusiastic acceptance of interrupts accounts for any real
bugs, but it definitely seems risky and unnecessary.

to insert the same key into a supposedly unique index.  The bug is of
low probability, and may not explain any of the recent reports of
duplicated rows; but a bug is a bug.

 token. Seems to be isolated to datetime.c and datetime.h.

values; it's not portable to call them with signed chars.  I recall doing
this for the last release, but a few more uncasted calls have snuck in.

> * Make locking of shared data structures more fine-grained

> * Change factorial to return a numeric

 when decoding date fields.

Update the list of recognized time zones.
Document the range of arguments allowed for SET TIME ZONE.
Still need to add info on other date/time symbols (e.g. "AM", "T")
 and to freshen the docs on the date/time parsing rules.

 cases which should have worked but did not.
Now supports julian day (J2452271), ISO time labels (T040506) and various
 combinations of spaces and run-togethers of dates, times, and time zones.
All regression tests pass, and I have more tests to add after the 7.2
 release (don't want to require changes to the ancillary horology result
 files until after then).

---
> * Allow queries across multiple databases [crossdb]

> * Change DEBUG startup tag to NOTICE;  change NOTICE to output to client
>   only if client exists (Bruce)

This item is not done:

< * -Make elog(LOG) in WAL its own output type, distinct from DEBUG (Peter E)
---
> * Make elog(LOG) in WAL its own output type, distinct from DEBUG

> * Add --port flag to regression tests

> * Change FIXED_CHAR_SEL to 0.20 from 0.04 to give better selectivity (Bruce)

> * Report failure to find readline or zlib at end of configure run

> 	o Change syntax to WITH DELIMITER, (keep old syntax around?)

> * Add WAL index reliability improvement to non-btree indexes

< * Improve access-permissions check on data directory in CYGWIN (Tom)
---
> * Improve access-permissions check on data directory in Cygwin (Tom)

<
---
> * Improve access-permissions check on data directory in CYGWIN (Tom)

'volatile' pointers to access those structures, so that optimizing
compilers will not decide to move the structure accesses outside of the
spinlock-acquire-to-spinlock-release sequence.  There are no known bugs
in these uses at present, but based on bad experience with lwlock.c,
it seems prudent to ensure that we protect these other uses too.
Per pghackers discussion around 12-Dec.  (Note: it should not be
necessary to worry about structures protected by LWLocks, since the
LWLock acquire and release operations are not inline macros.)