This resource is no longer available
What does high availability actually mean when you’re discussing Postgres clusters?
Sure, you can set an RPO, RTO, and SLA regarding expectations and deliverables, but what are you trying to achieve? Fast failover? No lost transactions? Both? What about time necessary to rebuild or reclaim a former Primary node? How do all of your various replication configurables affect this?
Discover the answers to all of these questions—and more—in the following blog post, which demystifies the Postgres high availability conversation.