Required by newest versions of DocBook and style sheets.

Use memcpy() rather than StrNCpy() which had forced a string termination
 character at the end.

of 2 to save a few cycles in md.c.  So, make it 2^30 not 10^9.

configuration constant to config.h.

(may be used while vacuuming unique btree-s).

2gig.  Fix failure to reliably put the smaller relation on the inside of
a hashjoin.

hpux_gcc too?

hardwired assumption.

called through fmgr.  Someday we should try to actually execute the function,
but that looks like it might be a major feature addition.
Not something to try during beta phase.

polygon rtree, circle rtree indexes.

would sometimes generate a plan that omitted a sort step before merge.

parameters in CREATE USER.

it with configure-script tests to see whether const, inline, volatile, etc
work or not.  (Curiously, configure was already doing the work to see if
const and inline were OK, but the results were not getting plugged into
config.h :-(.)

complaints (and some of my own).

autoconf 2.13.

 completion as required by the newest DocBook conventions.

Had been omitted from the integrated doc for no good reason.

1. Fix problems of PAGER and \? command
2. Add -E option that shows actual queries sent by \dt and friends
3. Add version number in startup banners for psql

There are two subdirectories (ISO8859-7 and koi8-to-win1251) containing
tests for Greek locale and server<=>client recoding feature (recently
submitted by Tatsuo Ishii <t-ishii@sra.co.jp>; we've debugged his patches
together in the field of Cyrillic support).

more portable way.

function is found in prosrc field of pg_proc, not proname.  This allows
multiple aliases of a built-in to all be implemented as direct builtins,
without needing a level of indirection through an SQL function.  Replace
existing SQL alias functions with builtin entries accordingly.
Save a few K by not storing string names of builtin functions in fmgr's
internal table (if you really want 'em, get 'em from pg_proc...).
Update opr_sanity with a few more cross-checks.

2. Much faster btree tuples deletion in the case when first on page
   index tuple is deleted (no movement to the left page(s)).
3. Remember blkno of new root page in BTPageOpaque of
   left/right siblings when root page is splitted.

related tables.

and related tables.

and newly expanded opr_sanity tests.

regress test 'type_sanity'.

It still doesn't do anything, but at least now it does nothing correctly.

Apparently, whatever these things used to link to got recycled into
something else ... but the dependent entries didn't.

use NOT EXISTS() which is a lot faster than NOT IN (),
update documentation.

configure, instead of having a bunch of crufty platform-specific guesses.