Best practices for a 2-node Patroni + PostgreSQL cluster with a external/witness DCS

From: Pratik Pandit <pratikpandit5322(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Best practices for a 2-node Patroni + PostgreSQL cluster with a external/witness DCS
Date: 2026-06-03 18:20:27
Message-ID: CAFchsDX8Wt9Emwx1ESYSx0x+w7GZYLu=mjh3QfNRxcWe9kKR6A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello PostgreSQL Community,

I am planning to set up a high-availability PostgreSQL cluster using
Patroni. Due to infrastructure constraints, I only have two dedicated
database nodes available.
I know that a Distributed Configuration Store (like etcd or Consul)
requires an odd number of nodes (minimum 3) to achieve quorum and safely
prevent split-brain scenarios.

Before I begin the deployment, I would appreciate your advice on the
following architectural approaches:
1. Is it recommended to run a 3-node etcd cluster where 2 instances live
on the DB nodes and a 3rd "witness" instance lives on a lightweight
application server/VM?
2. Alternatively, does Patroni safely support a 2-node setup using a single
external DCS instance, or does that introduce a critical single point of
failure (SPOF)?

Any architectural pointers or template configurations for this constraint
would be highly appreciated.
Thanks!

Browse pgsql-admin by date

  From Date Subject
Next Message Pratik Pandit 2026-06-03 18:26:36 Configuring Pacemaker constraints for Postgres on Shared Storage
Previous Message Alicja Kucharczyk 2026-06-03 12:32:41 Re: Any known bugs with respect to data corruption in pg12/pg 14