Skip to content

Commit 9963d28

Browse files
twk3ereadaxilleasjfarmiloe-rgb
committed
Merge branch 'docs-jfarmiloe-max-connections' into 'master'
Reword max connections check See merge request https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/7055 Merged-by: DJ Mountney <[email protected]> Approved-by: DJ Mountney <[email protected]> Approved-by: Evan Read <[email protected]> Co-authored-by: Evan Read <[email protected]> Co-authored-by: Achilleas Pipinellis <[email protected]> Co-authored-by: Justin Farmiloe <[email protected]>
2 parents 91e0f55 + 08d449b commit 9963d28

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

doc/settings/database.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -712,8 +712,10 @@ this.
712712

713713
In GitLab 16.0, GitLab defaults to using two database connections that point to the same PostgreSQL database.
714714

715-
Prior to upgrading to GitLab 16.0, you can check that PostgreSQL `max_connections` is high enough
716-
(using more than 50% of the available max connections).
715+
Before upgrading to GitLab 16.0, check that the PostgreSQL `max_connections` setting is high enough so that more than 50% of available connections show as being unused.
716+
For example, if `max_connections` is set to 100 and you see 75 connections in use, you must increase `max_connections` to at least 150 before upgrading because after
717+
upgrading, the in-use connections will double to 150.
718+
717719
You can verify this by running the following Rake task:
718720

719721
```shell

0 commit comments

Comments
 (0)