gitlab
/
omnibus-gitlab
mirror of https://gitlab.com/gitlab-org/omnibus-gitlab.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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: Fiona Neill <fneill@gitlab.com>
Approved-by: Fiona Neill <fneill@gitlab.com>
Co-authored-by: Manoj M J <mmj@gitlab.com>
This commit is contained in:
Fiona Neill 2024-04-29 13:24:20 +00:00
parent 6fab34cacb 9be1159647
commit 59cb03c01c
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/settings/database.md
View File

@ -590,16 +590,6 @@ sudo gitlab-rake gitlab:db:decomposition:connection_status
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