Package: repmgr
Version: 2.0-3
Severity: important
Tags: patch
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
testing repmgr and failing without having to copy/reproduce files in
the postgresql data directory by hand
* What exactly did you do (or not do) that was effective (or
ineffective)?
clone a master postgresql server and testing a failover.
* What was the outcome of this action?
the postgresql server on the slave refused to start due to missing
directory.
* What outcome did you expect instead?
a proper failover to happen.
This bug was fixed in a newer version of repmgr upstream and is only 2
characters long:
https://github.com/2ndQuadrant/repmgr/commit/e40b9db0a6e2cbe56df40a6fda115858cf3c790f
the 2.x version used in debian stable is however nolonger considered the
latest stable upstream.
Thanks for fixing.
-- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages repmgr depends on:
ii libc6 2.19-18+deb8u4
ii libpq5 9.4.8-0+deb8u1
ii postgresql-common 165+deb8u1
ii rsync 3.1.1-3
repmgr recommends no packages.
repmgr suggests no packages.
-- no debconf information
