From 72fe32c37fd3cf615c368f0344edad310e425031 Mon Sep 17 00:00:00 2001
From: Drew DeVault <sir@cmpwn.com>
Date: Tue, 30 Jun 2020 12:06:43 -0400
Subject: Add mock scenario to PSQL planning

---
 ops/robust-psql.md | 1 +
 1 file changed, 1 insertion(+)

(limited to 'ops')

diff --git a/ops/robust-psql.md b/ops/robust-psql.md
index a3c8d7c..69ad2ec 100644
--- a/ops/robust-psql.md
+++ b/ops/robust-psql.md
@@ -138,6 +138,7 @@ pgbouncer or pgpool. Then we should play out the following scenarios:
 - Promoting the secondary to the primary
 - Shut down the primary or secondary without pre-preparation
 - Accessing the database state at an arbitrary point in the past
+- Bringing the secondary back up to date after a primary outage
 - Major and minor version upgrades (pg 11 to 12)
 - Host OS upgrades (Alpine 3.11 to 3.12 or edge)
 - Cause a ZFS resliver on the primary and monitor database performance: does
-- 
cgit