to work everywhere.  Also, on FreeBSD you need to set the optreset variable
to 1 before parsing the command line a second time with getopt().

(The test 'make --version' with FreeBSD make (and potentially others)
would just reinvoke make on the same Makefile, resulting in an infinite
loop.)

to get platform-independent results.

the default target in GNUmakefile is reached.  This patch calls that
default target.

Pete Forman

Add more tests for JOIN syntax.
All tests pass on my Linux box (except for the usual couple of lines
 for geometry).

Update catalog version to today.

 Previously, all fields were unsigned, with only a trailing "ago" to
 indicate negative intervals. Now, ISO format does not use "ago", and
 and the traditional PostgreSQL format has the first numeric field unsigned
 with "ago" supporting that field. So "1 month - 2 days ago" is two days
 less than a month in the past.
Fix interval arithmetic across daylight savings time boundaries.
 Previously, most math across boundaries introduced a one hour offset.
Allow some date/time functions to return NULL if called with NULL args.
Implement functions for AT TIME ZONE support.
Support "SAT" as an Australian time zone if USE_AUSTRALIAN_RULES
 is defined.

 AT is now a keyword but is not a reserved word.

 any available string type. Previously, all candidate choices must have
 fallen within the same "type category" for PostgreSQL to be willing to
 choose any of them.
Need to apply the same fixup to operator type resolution.

Auto removing of offline log files and creating new file
at checkpoint time.

standard installation layout it should be possible to build the HTML
and print documentation without additional manual setup.

got confused by 'dummy' targetlist built for the UNION's toplevel query.
Fix by making dummy targetlist a little less cheesy.

the grammar did not allow redundant parentheses around sub-selects.
Distinguish LIMIT ALL from LIMIT 0; make the latter behave as one would
expect.

definitions using inherited columns in the
create table statement.

Stephan Szabo

confused in src/interfaces/libpq for some reason.  Seemingly, different
GNU make versions have several mutually conflicting problems with implicit
rule chains.  Words are not sufficient...

compilers from different providers.  (Especially important since the
C++ compiler that goes with your favourite C compiler might not work.)

says.

around anymore.

it to an absolute path.

target files in implicit rule chains.  That might have been a cool idea
but it seems to be too buggy to work, as it caused spurious recompiles in
several places.

from an ACL list if it had no permissions remaining, which confused
aclcheck terribly.  Also clean up code a little.

included, and then include <strings.h> if so.  Several systems already
needed <strings.h> anyway.  Some new systems that claim to conform to the
Unix 9x "standard" do not declare str[n]casemp() in string.h, and C99
compilers will not like that.