Skip to content

Commit

Permalink
docs: clarify behavior of primaryUpdateStrategy for single-instance c…
Browse files Browse the repository at this point in the history
…lusters (cloudnative-pg#5001)

Clarified the behavior of primaryUpdateStrategy when applied to a
cluster consisting of a single instance.

Signed-off-by: Pierrick <[email protected]>
(cherry picked from commit 893c61a)
  • Loading branch information
pchovelon committed Dec 6, 2024
1 parent 5118173 commit 3dea456
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/src/installation_upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,10 @@ plugin for `kubectl`.
!!! Important
In case `primaryUpdateStrategy` is set to the default value of `unsupervised`,
an upgrade of the operator will trigger a switchover on your PostgreSQL cluster,
causing a (normally negligible) downtime.
causing a (normally negligible) downtime. If your PostgreSQL Cluster has only one
instance, the instance will be automatically restarted as `supervised` value is
not supported for `primaryUpdateStrategy`. In either case, your applications will
have to reconnect to PostgreSQL.

Since version 1.10.0, the rolling update behavior can be replaced with in-place
updates of the instance manager. The latter don't require a restart of the
Expand Down

0 comments on commit 3dea456

Please sign in to comment.