Skip to content
Snippets Groups Projects
Commit 7d662d1a authored by Fiona Neill's avatar Fiona Neill
Browse files

Merge branch 'mmj-multi-db' into 'master'

Update Docs: 17.0 Remove support for single database connection

See merge request https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/7570



Merged-by: default avatarFiona Neill <fneill@gitlab.com>
Approved-by: default avatarFiona Neill <fneill@gitlab.com>
Co-authored-by: default avatarManoj M J <mmj@gitlab.com>
parents 1f5db99c 750fed4c
No related branches found
No related tags found
2 merge requests!144heptapod#1622: making 17.0 the oldstable,!127Merge upstream Omnibus GitLab into Omnibus Heptapod
......@@ -590,16 +590,6 @@
If the task indicates that `max_connections` is high enough, then you can proceed with the upgrade.
If, for any reason, you wish to remain on single connection, and you are upgrading
from GitLab 15.11 or earlier to GitLab 16.0, or switch back to single database connection
update this setting in `/etc/gitlab/gitlab.rb`:
```ruby
gitlab_rails['databases']['ci']['enable'] = false
```
In a multi-node environment, this setting should be updated on all Rails and Sidekiq nodes.
## Using a non-packaged PostgreSQL database management server
By default, GitLab is configured to use the PostgreSQL server that's included
......
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