will be released by transaction abort before _bt_end_vacuum gets called.
If either of these "can't happen" errors actually happened, we'd freeze up
trying to acquire an already-held lock.  Latest word is that this does
not explain Martin Pitt's trouble report, but it still looks like a bug.

pg_valid_server_encoding() returns the same result if the encoding is
valid.

ITAGAKI Takahiro

* Reduce storage space for small NUMERICs
>   http://archives.postgresql.org/pgsql-patches/2007-02/msg00505.php

> * Reduce storage space for small NUMERICs
>
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php
>

< 	o Add more logical syntax CLUSTER table USING index;
> 	o Add more logical syntax CLUSTER table USING index;

        o Add more logical syntax CLUSTER table USING index;
< 	o Add more logical syntax CLUSTER table ORDER BY index;
> 	o Add more logical syntax CLUSTER table USING index;

required memory context when handling client-specified parameter types
for an unnamed statement.  Per report from Kris Jurka.

 ecpglib supports it.
Change configure (patch from Bruce) and msvc build system to no longer require
 pthreads on win32, since all parts of postgresql can be thread-safe using the
 native platform functions.

  win32 threads.
- Fixed regression tests to run threading tests.

--- Simon.
Also, code review and cleanup for the previous COPY-no-WAL patches --- Tom.

properties of the "text" type, and then simplify the code accordingly.
Patch from Jeremy Drake.

from PuTTY with is under minimal BSD/MIT license. Marko Kreen.

its table list and then rechecks pgstat before vacuuming each table to
verify that no one has vacuumed the table in the meantime.

In the current autovacuum world this only means that a worker will not
vacuum a table that a user has vacuumed manually after the worker started.
When support for multiple autovacuum workers is introduced, this will reduce
the probability of simultaneous workers on the same database doing redundant
work.

ITAGAKI Takahiro

* Automatically create rules on views so they are updateable, per SQL99
>   http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php

seen by code inspecting the expression.  The best way to do this seems
to be to drop the original representation as a function invocation, and
instead make a special expression node type that represents applying
the element-type coercion function to each array element.  In this way
the element function is exposed and will be checked for volatility.
Per report from Guillaume Smet.

table entries to a separate routine.  Don't pass the pgstat database entry to
do_autovacuum; rather, have it fetch it by itself.

< * %Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
<   pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
<
<   These would be for application use, not for use by pg_dump.
<

>
> * Allow configuration of backend priorities via the operating system
>
>   Though backend priorities make priority inversion during lock
>   waits possible, research shows that this is not a huge problem.
>   http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php

Marko Kreen

mention cvsup last.

* Improve dead row detection during multi-statement transactions usage

> * Increase the number of rows recognized as dead during multi-statement
>   transactions
>
>   http://archives.postgresql.org/pgsql-patches/2007-03/msg00358.php
>

instructions from Berkeley.

A DBA is allowed to create a language in his database if it's marked
"tmpldbacreate" in pg_pltemplate.  The factory default is that this is set
for all standard trusted languages, but of course a superuser may adjust
the settings.  In service of this, add the long-foreseen owner column to
pg_language; renaming, dropping, and altering owner of a PL now follow
normal ownership rules instead of being superuser-only.
Jeremy Drake, with some editorialization by Tom Lane.

Magnus Hagander. Also, now it ignores space symbol after stopwords.

and GB18030. patches from ITAGAKI Takahiro.

Per report from Jim Rosenberg.  This possibly should get back-patched,
but I'm a bit suspicious of it still because of the lack of prior reports.

table constraints are changed; this is no longer true now that we
have a plan invalidation mechanism.

reset event, namely invalidate everything.  This oversight probably
explains the rare failures that some buildfarm machines have been
showing for the plancache regression test.