Very few out-of-the-box installations adequately represent the needs of every potential user. As a result, repmgr relies more on command invocation than on configuration parameters.
As a result, repmgr functions in far more environments than it normally would. There are organizations that use a VIP to always track the current primary node, as we will soon demonstrate. There are others that prefer reconfiguring PgBouncer hosts instead. Still others rely on F5 load balancers, CNAME assignment, or any number of other abstraction techniques.
Rather than dictate which is the preferred method, repmgr allows all of these to flourish as necessary based on user needs. In fact, repmgr offers quite a few parameters that accept a script or another kind of command to manage cluster operations. There's even an event handler to act as a routing engine for...
