Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
GitLab
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
GitLab
Commits
d7e8caee
Commit
d7e8caee
authored
2 years ago
by
Hossein Pursultani
Browse files
Options
Downloads
Patches
Plain Diff
Fix linter error
parent
a338d24d
No related branches found
No related tags found
1 merge request
!103891
Document near zero downtime PostgreSQL major upgrade for Patroni cluster
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/administration/postgresql/replication_and_failover.md
+1
-1
1 addition, 1 deletion
doc/administration/postgresql/replication_and_failover.md
with
1 addition
and
1 deletion
doc/administration/postgresql/replication_and_failover.md
+
1
−
1
View file @
d7e8caee
...
...
@@ -1085,7 +1085,7 @@ then reverting the leader, and finally reverting the replicas.
With Patroni it is possible to run a major PostgreSQL upgrade without shutting down the cluster. However, this will
require additional resources to host the new Patroni nodes with the upgraded PostgreSQL. In practice, with this
procedure, you are creating a new Patroni cluster with a new version of PostgreSQL and
and
migrating the data from the
procedure, you are creating a new Patroni cluster with a new version of PostgreSQL and migrating the data from the
existing cluster. This procedure is non-invasive and does not impact your existing cluster before switching it off. But
this can be both time and resource consuming and you should consider their trade-off with availability.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment