diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-29 21:10:24 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-29 21:10:24 +0300 |
| commit | 3e3f936ff7e5645fc5d379aae87dca6671dc417f (patch) | |
| tree | 667221ef19830ea955035580bf0a6487dc610584 /doc/administration/postgresql | |
| parent | 9a8093da816c96e2bab9812c2f00ef276270793b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/postgresql')
| -rw-r--r-- | doc/administration/postgresql/replication_and_failover.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/postgresql/replication_and_failover.md b/doc/administration/postgresql/replication_and_failover.md index c547e5c3638..a1fc8c49ee3 100644 --- a/doc/administration/postgresql/replication_and_failover.md +++ b/doc/administration/postgresql/replication_and_failover.md @@ -1086,7 +1086,7 @@ Reverting the PostgreSQL upgrade with `gitlab-ctl revert-pg-upgrade` has the sam `gitlab-ctl pg-upgrade`. You should follow the same procedure by first stopping the replicas, then reverting the leader, and finally reverting the replicas. -### Near zero downtime upgrade of PostgreSQL in a Patroni cluster (Experimental) +### Near zero downtime upgrade of PostgreSQL in a Patroni cluster **(EXPERIMENT)** Patroni enables you to run a major PostgreSQL upgrade without shutting down the cluster. However, this requires additional resources to host the new Patroni nodes with the upgraded PostgreSQL. In practice, with this |