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)

Configuring HAProxy for the multi-master approach

Though we already have an entire chapter on proxy and load balancing techniques Chapter 4, Proxy and Pooling Resources, some of these concepts change slightly in a multi-master context.

Consider the implications of attempting to use simple round-robin query distribution. If our application reconnects for each operation and inserts data into Node A, but then selects from Node B, this is an implicit race condition that may not be satisfied at that specific time.

This can also produce strange effects if the application is stateless and performs SELECTUPDATE pairs regardless of which node it is communicating with. In the presence of high latency for any reason, this could result in two different sequential incremental updates on the same base value.

This recipe will explain how to alter our previous HAProxy configuration to...