Skip to content

Commit 9be1159

Browse files
Manoj M JFiona Neill
authored andcommitted
Update Docs: 17.0 Remove support for single database connection
1 parent 1f0bfa5 commit 9be1159

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed

doc/settings/database.md

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -590,16 +590,6 @@ sudo gitlab-rake gitlab:db:decomposition:connection_status
590590
591591
If the task indicates that `max_connections` is high enough, then you can proceed with the upgrade.
592592
593-
If, for any reason, you wish to remain on single connection, and you are upgrading
594-
from GitLab 15.11 or earlier to GitLab 16.0, or switch back to single database connection
595-
update this setting in `/etc/gitlab/gitlab.rb`:
596-
597-
```ruby
598-
gitlab_rails['databases']['ci']['enable'] = false
599-
```
600-
601-
In a multi-node environment, this setting should be updated on all Rails and Sidekiq nodes.
602-
603593
## Using a non-packaged PostgreSQL database management server
604594
605595
By default, GitLab is configured to use the PostgreSQL server that's included

0 commit comments

Comments
 (0)