Re: How to configure Repmgr

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "Tharmarajah, Sam" <sambavan(dot)tharmarajah(at)usask(dot)ca>
Cc: Jwiencek3 <jwiencek3(at)comcast(dot)net>, jacob ndinkwa <jndinkwa(at)gmail(dot)com>, Loles <lolesft(at)gmail(dot)com>, Zhaoxun Yan <yan(dot)zhaoxun(at)gmail(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: How to configure Repmgr
Date: 2024-01-12 16:59:10
Message-ID: CANzqJaBapgBcpiEzvO5JhboEK5bNHrUfO-roUWKOUFjprQtrAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Fri, Jan 12, 2024 at 11:32 AM Tharmarajah, Sam <
sambavan(dot)tharmarajah(at)usask(dot)ca> wrote:

> Not sure of the purpose of going with repmgr. We have been using repmgr
> and my personal resentment with it is that every time there is a network
> issue, we end up with two primary and manual intervention is needed to
> overcome that.
>

That's to be expected with only two nodes. You can "fix" that by adding a
third node for quorum. (It doesn't even need Postgresql on it; just has to
"be there", and running heartbeat software.)

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2024-01-12 22:43:57 Re: Synchronous Replication: Where is data visible first?
Previous Message Tharmarajah, Sam 2024-01-12 15:32:07 RE: How to configure Repmgr