Skip to content
Snippets Groups Projects
Commit b51df68e7cb7 authored by Alvin Gounder's avatar Alvin Gounder
Browse files

Remove the GitLab 18.0 guidance for splitting db

parent 1ebac4629941
No related branches found
No related tags found
1 merge request!168Merge upstream Omnibus GitLab up to the 17.6 branching point
......@@ -592,7 +592,7 @@
### Configuring multiple database connections
> - The `gitlab:db:decomposition:connection_status` Rake task was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/111927) in GitLab 15.11.
> - Support for single database will be [removed in GitLab 18.0](https://docs.gitlab.com/ee/update/deprecations.html#running-a-single-database-is-deprecated).
> - Support for single database will be [removed in a future release](https://docs.gitlab.com/ee/update/deprecations.html#running-a-single-database-is-deprecated).
In GitLab 16.0, GitLab defaults to using two database connections that point to the same PostgreSQL database.
......
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