Book Image

PostgreSQL 12 High Availability Cookbook - Third Edition

By : Shaun Thomas
Book Image

PostgreSQL 12 High Availability Cookbook - Third Edition

By: Shaun Thomas

Overview of this book

Databases are nothing without the data they store. In the event of an outage or technical catastrophe, immediate recovery is essential. This updated edition ensures that you will learn the important concepts related to node architecture design, as well as techniques such as using repmgr for failover automation. From cluster layout and hardware selection to software stacks and horizontal scalability, this PostgreSQL cookbook will help you build a PostgreSQL cluster that will survive crashes, resist data corruption, and grow smoothly with customer demand. You’ll start by understanding how to plan a PostgreSQL database architecture that is resistant to outages and scalable, as it is the scaffolding on which everything rests. With the bedrock established, you'll cover the topics that PostgreSQL database administrators need to know to manage a highly available cluster. This includes configuration, troubleshooting, monitoring and alerting, backups through proxies, failover automation, and other considerations that are essential for a healthy PostgreSQL cluster. Later, you’ll learn to use multi-master replication to maximize server availability. Later chapters will guide you through managing major version upgrades without downtime. By the end of this book, you’ll have learned how to build an efficient and adaptive PostgreSQL 12 database cluster.
Table of Contents (17 chapters)

Incorporating a repmgr witness

As we discussed in Chapter 1, Architectural Considerations, it is incredibly important to include an odd number of nodes in most cluster designs. Generally, this is necessary to guarantee that a voting quorum can be established in the case that the primary node becomes unavailable. We must choose one existing standby system to promote and take over the cluster.

We must also consider the possibility of split-brain and network partitions. Witness nodes help protect us from these scenarios by acting as an objective third party. If they are located in the same data center as the current primary, then the network partitions will prevent it from voting at all, and we will be protected from network partitions. If it's in a tertiary data center away from either the current primary or standby, there will be two independent routes to verify whether or...