aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDrew DeVault <sir@cmpwn.com>2020-06-30 15:33:00 -0400
committerDrew DeVault <sir@cmpwn.com>2020-06-30 15:33:00 -0400
commit9267b77dc67472bec73ce3f1f7ff52c3f909587f (patch)
tree6437af76580b1add886f6032eb25b67b74eaf7c7
parent3989b843a26c525fd9a362ab41f7d05638308501 (diff)
downloadsr.ht-docs-9267b77dc67472bec73ce3f1f7ff52c3f909587f.tar.gz
psql: fix typo
-rw-r--r--ops/robust-psql.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/ops/robust-psql.md b/ops/robust-psql.md
index 8da7448..256a8af 100644
--- a/ops/robust-psql.md
+++ b/ops/robust-psql.md
@@ -234,7 +234,7 @@ We should play out the following scenarios:
- Bringing the standby 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
+- Cause a ZFS resilver on the primary and monitor database performance: does
this trigger a "soft outage" where performance is awful but the database is
ostensibly online?