Skip to content
Snippets Groups Projects
Commit 579491848223 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis
Browse files

Merge branch 'doc-psureshbabu-master-patch-04433' into 'master'

Add information about external Postgres upgrade and correct the restore instructions

See merge request gitlab-org/omnibus-gitlab!5425
3 merge requests!51Validate shift of Heptapod 0.25 to oldstable series,!47Making Heptapod 0.25 the new stable in Omnibus,!45GitLab 14.2
...@@ -772,6 +772,13 @@ ...@@ -772,6 +772,13 @@
### Upgrade a non-packaged PostgreSQL database ### Upgrade a non-packaged PostgreSQL database
You can upgrade the external database as suggested by the provider after stopping all the processes that are connected to the database (Puma, Sidekiq):
```shell
sudo gitlab-ctl stop puma
sudo gitlab-ctl stop sidekiq
```
Before proceeding with the upgrade, note the following: Before proceeding with the upgrade, note the following:
- Before upgrading, review the [GitLab and PostgreSQL version compatibility table](../package-information/postgresql_versions.md) - Before upgrading, review the [GitLab and PostgreSQL version compatibility table](../package-information/postgresql_versions.md)
...@@ -823,7 +830,7 @@ ...@@ -823,7 +830,7 @@
1. Shutdown the PostgreSQL 11 database host. 1. Shutdown the PostgreSQL 11 database host.
1. Edit `/etc/gitlab/gitlab.rb` and update the `gitlab_rails['db_host']` setting 1. Edit `/etc/gitlab/gitlab.rb` and update the `gitlab_rails['db_host']` setting
to point to the PostgreSQL database 11 host. to point to the PostgreSQL database 12 host.
1. Reconfigure GitLab: 1. Reconfigure GitLab:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment