gitlab:db:decomposition:connection_status Rake task doesn't include connection info after ci: database has been created

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

gitlab-rake gitlab:db:decomposition:connection_status shows the used and max connections of the Postgres database as long as the ci: section hasn't been created:

❯ gitlab-rake gitlab:db:decomposition:connection_status
Currently using 42 connections out of 1337 max_connections,
which is enough for running GitLab using two database connections.

This is pretty useful information to have. That behavior changes once the ci: section has been created to display a static message: https://gitlab.com/gitlab-org/gitlab/-/blob/v16.6.1-ee/lib/tasks/gitlab/db/decomposition/connection_status.rake?ref_type=tags#L8-11

❯ gitlab-rake gitlab:db:decomposition:connection_status
GitLab database already running on two connections

Proposal

Provide the connection info, even post ci: migration:

❯ gitlab-rake gitlab:db:decomposition:connection_status
GitLab database already running on two connections

Currently using 42 connections out of 1337 max_connections,
which is enough for running GitLab using two database connections.

Intended users

Sidney (Systems Administrator) wants to check whether their Postgres max_connections is sufficient to accommodate the increased connection demand of GitLab ter the deprecation of "single database connection".

Feature Usage Metrics

Does this feature require an audit event?

No.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.