From 83c8518231ccdc60ae7cd1fb1d4538d059bf400b Mon Sep 17 00:00:00 2001
From: Anton Smith <asmith@gitlab.com>
Date: Fri, 1 Dec 2023 10:01:18 +0000
Subject: [PATCH] Mention restarting PSQL can resume replication

---
 doc/administration/geo/index.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/administration/geo/index.md b/doc/administration/geo/index.md
index 171670b05bf24..0be06b08f4ddf 100644
--- a/doc/administration/geo/index.md
+++ b/doc/administration/geo/index.md
@@ -249,6 +249,8 @@ Pausing and resuming replication is done through a command-line tool from the no
 
 If `postgresql` is on a standalone database node, ensure that `gitlab.rb` on that node contains the configuration line `gitlab_rails['geo_node_name'] = 'node_name'`, where `node_name` is the same as the `geo_node_name` on the application node.
 
+Also, be aware that if PostgreSQL is restarted after pausing replication (either by restarting the VM or restarting the service with `gitlab-ctl restart postgresql`), PostgreSQL automatically resumes replication, which is something you wouldn't want during an upgrade or in a planned failover scenario.
+
 **To Pause: (from secondary)**
 
 ```shell
-- 
GitLab