> * Allow finer control over the caching of prepared query plans
>
>   Currently, queries prepared via the libpq API are planned on first
>   execute using the supplied parameters --- allow SQL PREPARE to do the
>   same.  Also, allow control over replanning prepared queries either
>   manually or automatically when statistics for execute parameters
>   differ dramatically from those used during planning.
>

Gavin Sherry

compliance with SQL2003 spec syntax.

Oliver Jowett

and doesn't process forward slashes in the same way as external
commands.  Quoting the first argument to COPY does not convert forward
to backward slashes, but COPY does properly process quoted forward
slashes in the second argument.

Win32 COPY works with quoted forward slashes in the first argument only if the
current directory is the same as the directory of the first argument.

test only tests for building a binary, not building a shared library.

On Linux, you can build a binary with -pthread, but you can't build a
binary that uses a threaded shared library unless you also use -pthread
when building the binary, or adding -lpthread to the shared library
build.  This patch has the effect of doing the later by adding both
-pthread and -lpthread when building libpq.

a comment.

Jon Jensen

parser).

that refers to a now-deleted userid.  Per gripe from Chris Ochs.

the server version number.  This commit also removes bogus DOS line
endings from libpqddll.def.

Greg Sabino Mullane

Thanks to Michael Fuhr for identifying the problem.

it with previous prototype to suppress complaints from picky compilers,
per report from Scott Bailey.  Also, remove substitute strerror
definition --- not needed, since we link this with libpgport.

for transaction commits that occurred just before the checkpoint.  This is
an EXTREMELY serious bug --- kudos to Satoshi Okada for creating a
reproducible test case to prove its existence.

produced no rows. Now it returns 0 rows instead. Adjusted regression
test for this case.

'make install' on OS X.  Per suggestion from Adam Witney.

< * Allow DELETE to handle table aliases for self-joins
> * Allow an alias to be provided for the target table in UPDATE/DELETE
276,279c276,282
<   There is no way to create a table alias for the deleted table for use
<   in the DELETE WHERE clause.  The agreed approach is to allow a USING
<   clause to specify additional tables.  UPDATE already has an optional
<   FROM clause for this purpose.
>   This is not SQL-spec but many DBMSs allow it.
>
> * Allow additional tables to be specified in DELETE for joins
>
>   UPDATE already allows this (UPDATE...FROM) but we need similar
>   functionality in DELETE.  It's been agreed that the keyword should
>   be USING, to avoid anything as confusing as DELETE FROM a FROM b.

* Add COMMENT ON for all cluster global objects (users, groups,
  databases and tablespaces)

time zone names we support.

< * Add COMMENT for tablespaces

> * Add COMMENT for tablespaces

of '.' or '..'.  Extend canonicalize_path() to trim off trailing occurrences
of these things, and use it to fix up paths where needed (which I think is
only after places where we trim the last path component, but maybe some
others will turn up).  Fixes Josh's complaint that './initdb' does not
work.

slashes to backslashes #ifdef WIN32.  This is to cope with the fact
that Windows seems exceedingly unfriendly to slashes in shell commands,
as per recent discussion.

to support PST8PDT time zone for the regression tests.

tag her configure 8.0.0beta1 ...

plpgsql EXCEPTION blocks.