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)

Proxy and Pooling Resources

Abstraction can protect a database from even the busiest platform and also ensure that applications always contact an online database server. Previous chapters in this book have already emphasized the importance of masquerading the primary database node to enable maintenance and availability. Two tools that are very popular for this purpose are virtual IP addresses and HAProxy software.

Yet there's always more to the story; abstraction isn't merely about indirection.

Modern applications, microarchitectures, and web services often involve hundreds or even thousands of servers and virtual machines (VMs). If we follow a simple and naive development cycle where applications have direct access to the database, each of these servers may require dozens of connections per program. Should each of these applications maintain their own connection pool...