tuples inserted/deleted/updated in a single transaction.  On my machine,
this reduced the time to delete 80000 tuples in a foreign-key-referencing
table from ~15min to ~8sec.

AC_SUBST that messed up the diversions and thus the configure output.

Respect default port setting in JDBC driver.
Pick up version number from Makefile.global.
Change installation directory to share/java/.
Document.

driver does not work because its internal cross-references get bound
to similarly named functions in unixODBC shared library.

psqlodbc.c's constructor-making techniques do not work.

of DSSSL.

under the postmaster --- specifically, if we are a standalone backend
running under the initdb script, this is critical!

2)Fix some memory leaks.
3)Change some bogus error messages.

handle this.

be allowed to receive ungrouped variables of the current query level.
Curious that no one reported this bug before...

of a counted input string.  Marinos Yannikos' recent crash report turns
out to be due to applying pg_ascii2wchar_with_len to a TEXT object that
is smack up against the end of memory.  This is the second just-barely-
reproducible bug report I have seen that traces to some bit of code
fetching one more byte than it is allowed to.  Let's be more careful
out there, boys and girls.
While at it, I changed the code to not risk a similar crash when there
is a truncated multibyte character at the end of an input string.  The
output in this case might not be the most reasonable output possible;
if anyone wants to improve it further, step right up...

succeeds or not.  Revise rtree page split algorithm to take care about
making a feasible split --- ie, will the incoming tuple actually fit?
Failure to make a feasible split, combined with failure to notice the
failure, account for Jim Stone's recent bug report.  I suspect that
hash and gist indices may have the same type of bug, but at least now
we'll get error messages rather than silent failures if so.  Also clean
up rtree code to use Datum rather than char* where appropriate.

One more :)) It's for improper function argumets for
PLTCL_UNKNOWN_SUPPORT code

I'm not an autoconf expert, but is it possible to enable unknown
support in pltcl with configure option ?
This support is really handy for real life usage of pl/tcl.

seva@sevasoft.kiev.ua

in splitting code:

seva@sevasoft.kiev.ua

directories, per suggestion from Robert Creager.

        - Removed org.postgresql.xa.Test from the JDBC EE driver as it's an old
          test class and prevented it from compiling.

- Prevent double-dumping of sequences when dataOnly.

- Change -U option to -L to allow -U to specify username in future. (pg_restore)