STANDBY CLONE should be run by a SUPERUSER, otherwise we won't be able
to retrieve data_directory and the other parameters we need by
querying the database.
Allow repmgr to obtain tablespace's locations from pg 9.2 and later
in which we no longer have a spclocation column in pg_tablespaces
getMasterConnection() cannot avoid checking the same node that asks
to find the master.
This was a micro optimization based on the fact that all commands that
needed to detect the master were executed from the standby but now that
we have CLUSTER level commands that is not true anymore
Add a CLUSTER CLEANUP command to clean monitor's history,
also include a --keep-history (-k) option to indicate how many
days of history to keep
Fix a few bugs introduced when merging features
Remove kludge added to create user and db for witness.
It's too fragile, almost always cause a "segment violation" and
don't seems to be very useful.
Remove a variable left in last commit
Force to enter a password for the superuser in the witness, this is
in case we need to send a password to connect as stated in
master's pg_hba.conf.
Fix CLUSTER CLEANUP, it needs to establish a local connection in order
to look for the master
Improve the version message to actually show the repmgr version not
only postgresql's one
Add a quick setup for autofailover
Add a check of the connection inside the CancelQuery() so it check
that before trying to cancel a query, which can block.
The release changed, just wait a little before setting it.
Also make well known names in HISTORY be only names, without
last name
Add an option for "no-history" mode, where repmgrd just checks the
conectivity of master but don't INSERT any data into it
Change Copyright date to cover 2012
Add release notes
Make the monitoring history capabilities of repmgr be optional and
turned off by default. Most of it has been superseeded by
pg_stat_replication view, we can still start it by using the switch
--monitoring-history
Change release notes because of commit bf241ba1d6f74ee2b816368e374986188237cba8
If master_response_timeout hasn't been set in repmgr.conf it defaults
to zero, which was causing to a false positive in the failure detection
logic in wait_connection_availability(). So, change that to defaults to 60s
and add a check to avoid it being set to zero or negative.

Problem reported and analyzed by Andrew Newman
Commit 2d24518d9db587d70770f9ec5f94238ae4a5c31d added an additional
'}' at the end of parse_config(). removing.