Prepare 3.3.0-beta1
autoreconf
Fix spelling error in debug message.
trivial fix of document
Fix paramater's name in pgpool.conf.sample*
Remove unnecessary file copy
Fix to include rpm_installer into tar ball.
Merge branch 'master' of ssh://git.postgresql.org/pgpool2
Register pgpool_regclass in pg_catalog schema.  This is necessary to
deal with clients which restricts schema search path to pg_catalog
only. Postgres_fdw is such a client.
Add regression test case for postgres_fdw.
Fix comment in create_failover_script() and create_follow_master_script().
Fix failover.sh to not cause shell error in certain cases.

If not all arguments are supplied (this could happen if no available
backend exists, for example), the script could fail.
Fix pgpool -m f stop" hang.

This is caused by unmanaged pgpool children remaining.  This could
happen if multiple PostgreSQL are going down (or even starting pgpool,
without starting PostgreSQL can easily trigger this).  Child calls
degenerate_backend_set() and it tries to aquire semaphore to write a
failover request. In this case the signal mask is set as well, thus
signals are never received. To fix this, kill pgpool children before
forking them.
Fix comment.
Add new regression test.
Fix pg_md5 command crash.

Fix contributed by Muhammad Usama(from [pgpool-hackers: 302])

While looking at the pgpool-II code I found a potential crash or stack
smash in pg_md5 utility.
The problem is update_pool_passwd() calls pg_md5_encrypt() function to get
the md5 password, and the password format generated by pg_md5_encrypt()
function is
"md5" followed by 32-hex digits, which sums up to 35 characters while the
host variable defined in update_pool_passwd() function to hold this
password can contain maximum 32 characters.
Fix memqcache segfaults reported in bug#63.

When a query executes and the query result is too large,
query_context->temp_cache is discarded the query result is not
committed to cache storage when the query completed. In extended query
mode, it is possible that the same query context is used for
subsequent bind/execute cycle through reusing the portal. Problem is,
query_context->temp_cache is already gone and a segfault is caused by
accessing the pointer. To fix this, when query_context->temp_cache is
discarded, set the pointer to NULL and whenever access
query_context->temp_cache, check it is NULL or not.
Add regression test for bug#63.
Fix segmentation fault of child that occurs when startup packet has
no PostgreSQL user information.

When a startup packet has no PostgreSQL user specified, pgpool-II
terminated abnormally. You can reproduce it by

 $ psql -p 9999 -U ''

If enable_pool_hba is on, a child process terminates by segmentation
fault. Otherwise if enable_pool_hba is off, the error message is

 ERROR: pool_discard_cp: cannot get connection pool for user (null) database (null)

In both cases, psql terminates with no message on frontend.

To resolve it, if PostgreSQL user is not specified in startup packet,
the message as following is output to both log and frontend. This is
the same behavior as PostgreSQL.

 FATAL: no PostgreSQL user name specified in startup packet
Add a tess for the previous commit