Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
omnibus-heptapod
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
heptapod
omnibus-heptapod
Commits
944e962549a9
Commit
944e962549a9
authored
1 year ago
by
GitLab Bot
Browse files
Options
Downloads
Plain Diff
Automatic merge of gitlab-org/omnibus-gitlab master
parents
8e05cbfd1e2f
0991400bf73e
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!100
Upstream Merge of 16.1 CE branching point
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/settings/database.md
+1
-1
1 addition, 1 deletion
doc/settings/database.md
with
1 addition
and
1 deletion
doc/settings/database.md
+
1
−
1
View file @
944e9625
...
...
@@ -709,7 +709,7 @@
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
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`
:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment