Commits on Jan 13, 2013
  1. Options -F -W -I -v doesn't accept arguments, which means that on

    getopt_long shouldn't be marked with the colon (:) character.
    This has been wrong since day one, so backpatching all the way until
    Jaime2ndQuadrant committed Jan 13, 2013
Commits on Jan 11, 2013
  1. If the node is a witness don't bother asking its position, it always

    will be 0/0. We just need to check that we can connect to it to determine
    if we are in the majority.
    Jaime2ndQuadrant committed Jan 11, 2013
Commits on Dec 19, 2012
  1. Fix a problem that caused a standby to promote itself without going to

    voting procedure.
    This is because of a race condition inside CheckPrimaryConnection().
    This has independently reported by Alex Railean and Dumitru, and Frank Jördens.
    Analyzed and fixed by Cédric Villemain.
    The fix have been verified to work by Frank
    Jaime2ndQuadrant committed Dec 19, 2012
Commits on Dec 11, 2012
Commits on Dec 3, 2012
  1. To select new master it needs to know which standby has received more

    xlog records from master, so it standby should use pg_last_xlog_receive_location()
    to report their positions. This solves a possible situation in which
    a standby that is considered as new master when promoted is no longer
    the best option.
    Jaime2ndQuadrant committed Dec 3, 2012
Commits on Nov 14, 2012
  1. Add an option for STANDBY FOLLOW to wait for a master to appear.

    This is important for autofailover to do the right thing when
    standbys detected master death at different times.
    While this is a new option, seems important for the autofailover
    to work properly so i will consider the lack of it a bug and
    will backpatch to 2.0 where autofailover was introduced.
    For gripe from Alex Railean, about a standby not finding the new
    master because the new master hasn't finish promoting.
    Jaime2ndQuadrant committed Nov 11, 2012
Commits on Nov 9, 2012
Commits on Sep 16, 2012
  1. Fix node decision logic when priorities are involved. Currently if

    two nodes with different prorities are equally good to be promoted
    the second one (with a lower priority, considering them
    in descending order) will win.
    Per report from Brailean Dumitru
    jcasanov committed Sep 16, 2012
  2. Add a comment

    jcasanov committed Sep 16, 2012
  3. Keep compiler quiet. Noted when compiling in FreeBSD in which i

    get a warning for an uninitialized variable.
    Also, define InvalidXLogRecPtr. We don't really need it but using
    it make the initialization future proof (considering that in 9.3
    XLogRecPtr will change its structure).
    jcasanov committed Sep 16, 2012
Commits on Sep 15, 2012
  1. When we have more command-line arguments than we should have we

    need to show that last value and we should use only optind for that
    instead of optind+1
    jcasanov committed Aug 30, 2012
  2. Fix documentation to always use -h sintax to refer to the node we

    want to clone or connect to, instead of relying on the fact that
    for some time putting that argument at last worked.
    jcasanov committed Aug 30, 2012
  3. Make repmgr compatible with FreeBSD.

    We need to add an #include and make it use a different path for the
    "true" binary.
    Maybe we need to make this changes for all BSD systems but having no
    evidence of that i prefer to make this only for systems with __FreeBSD__
    jcasanov committed Sep 15, 2012
Commits on Sep 11, 2012
Commits on Jul 27, 2012
  1. Fix tabs in HISTORY

    Jaime2ndQuadrant committed Jul 27, 2012
Commits on Jul 21, 2012
  1. Now that we can have no monitoring we need to check all nodes at fail…

    not only those in repl_monitor
    Jaime2ndQuadrant committed Jul 21, 2012
  2. Add tunables for connection retries to master and interval between

    connection retries, these parameters along with master_response_timeout
    determines the amount of time since failure to failover
    Jaime2ndQuadrant committed Jul 21, 2012
  3. Commit 2d24518 added an additional

    '}' at the end of parse_config(). removing.
    Jaime2ndQuadrant committed Jul 21, 2012
  4. 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
    Jaime2ndQuadrant committed Jul 21, 2012
Commits on Jul 6, 2012
  1. 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
    Jaime2ndQuadrant committed Jul 6, 2012
Commits on Jul 5, 2012
  1. Add release notes

    Jaime2ndQuadrant committed Jul 5, 2012
Commits on Jul 4, 2012
  1. Add an option for "no-history" mode, where repmgrd just checks the

    conectivity of master but don't INSERT any data into it
    Jaime2ndQuadrant committed Jul 4, 2012
Commits on Jul 2, 2012
  1. The release changed, just wait a little before setting it.

    Also make well known names in HISTORY be only names, without
    last name
    Jaime2ndQuadrant committed Jul 2, 2012
Commits on Jun 26, 2012
  1. Add a check of the connection inside the CancelQuery() so it check

    that before trying to cancel a query, which can block.
    Jaime2ndQuadrant committed Jun 26, 2012
Commits on Jun 16, 2012
Commits on Jun 15, 2012
  1. 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.
    Jaime2ndQuadrant committed Jun 15, 2012