Add new watchdog mode using heartbeat signal of udp packet in lifecheck
Fix to restart watchdog processes automatically when these exit abnormally.
Add options of watchdog UDP heartbeat mode to pgpoo.conf.sample.

The option names are tentative and might be changed.
Add interlocking mechanism of exclusive failover command execution

When using multiple pgpools with watchdog enabled, failover commands
(failover_command, failback_command, and follow_master_comman) get
executed only at one pgpool.

Previously, these command got executed at all pgpools.
Add interlocking mechanism of exclusive failover command execution

When using multiple pgpools with watchdog enabled, failover commands
(failover_command, failback_command, and follow_master_comman) get
executed only at one pgpool.

Previously, these command got executed at all pgpools.
Fix DROP OPERATOR FAMILY.
Fix scanner to set standard_confirming_strings = false. Now all
test/parser tests passed.

This was forgotten in the previous commit.
Remove root user check when watch is enabled.

Per discussion [pgpool-general: 1627] Re: watchdog root requirement.
Replace "sticky bit" to "setuid bit" in comments and funcation names

These words were used mistakenly and caused confusion.
Replace "sticky bit" to "setuid bit" in log message and funcation names

These words were used mistakenly and caused confusion.
Merge branch 'feature/watchdog_for_v3_3' of ssh://git.postgresql.org/pgpool2 into feature/watchdog_for_v3_3
Allow to set memqcache_oiddir.
Fix bug with on memory query cache in handling UPDATE/DELETE with table alias.

If UPDATE/DELETE is with table alias (UPDATE t1 AS foo...) pgpool
thinks the table name is "t1 AS foo" and fails to invalidate query
cache. This is caused by _outRangeVar() called from nodeToString()
which generates a query string from RangeVar node in raw parse
tree. The solution is removing "AS foo" part from the output of the
string. But reported in bugtrack #56.
Add authentication mechanism for watchdog packet communication

Watchdog packets from pgpool having wrong authentication key are
rejected. All pgpools must have the same key, which is specified
option wd_authkey in pgpool.conf. pgpool with wrong authkey can't
even start watchdog, because the startup packet is rejected by other
pgpools.
Fix to clear all the query cache on shared memory when standby pgpool escalates to active

This is aimed to prevent the new active pgpool from using inconsistent
query cache with the previous active
Add clear_memqcache_on_escalation option

If this is on, all the query caches on shared memory are cleared
when standby pgpool escalates to active (virtual IP holder).
This option should be off when clients connect to pgpool not using
virtual IP, such like multi-master configuration.
Add wd_escalation_command option

This specifies command which is executed at escalation on the new
active pgpool server before virtual IP is brought up.
Merge branch 'feature/watchdog_for_v3_3'

Conflicts:
	pool_config.c
Add mention about "-D" option.
Consider timeout waiting for compeletion of failback request in on line recovery.

This will prevent the recovery operation continues forever and we
cannot even shutdown pgpool main process. This could happen especially
while executing follow master command. At this moment, the timeout is
fixed value(5 seconds). This should be enough for the operation since
it does not imply any I/O or DB operation. Before it waited
forever. Problem is, it is possible that right after failover, the
failback request sent can be lost. In the long run we should fix it
but at this moment I prefer to band aid the problem because the fix
will not be trivial.