Goal Ensure that the combined database connection pools used by GitLab Rails/Puma, Sidekiq workers, and Workhorse never exceed the PostgreSQL server’s max_connections limit, preventing intermittent connection pool exhaustion under load. Constraints and uncertainty Each component exposes its own pool setting: gitlab_rails['db_pool'], sidekiq['db_pool'], and gitlab_workhorse['db_pool']. The documentation provides no automatic formula or validation to guarantee that the sum of these three values stays below postgresql['max_connections']. Administrators must manually calculate and adjust the values, which can lead to oversight and sporadic connection refusals during peak traffic. What is the recommended approach to validate that the combined pool sizes remain within the PostgreSQL limit? How can administrators automate detection of a potential overflow before applying configuration changes? Should GitLab introduce a built‑in check or warning when the sum of the three pools exceeds the configured postgresql['max_connections']?

GitLab DB Pool Limit Validation

GitLab database pool configuration: missing cross‑component limit enforcement

0 reputation · 24 Oct 2022, 10:20 UTC

59.1K views0

Goal

Ensure that the combined database connection pools used by GitLab Rails/Puma, Sidekiq workers, and Workhorse never exceed the PostgreSQL server’s max_connections limit, preventing intermittent connection pool exhaustion under load.

Constraints and uncertainty

Each component exposes its own pool setting: gitlab_rails['db_pool'], sidekiq['db_pool'], and gitlab_workhorse['db_pool'].
The documentation provides no automatic formula or validation to guarantee that the sum of these three values stays below postgresql['max_connections'].
Administrators must manually calculate and adjust the values, which can lead to oversight and sporadic connection refusals during peak traffic.

What is the recommended approach to validate that the combined pool sizes remain within the PostgreSQL limit?

How can administrators automate detection of a potential overflow before applying configuration changes?

Should GitLab introduce a built‑in check or warning when the sum of the three pools exceeds the configured postgresql['max_connections']?

Keep exploring this topic

Bun SQLite module: missing connection pool size configuration

Developers using Bun's built‑in SQLite module need a way to cap the number of concurrent database connections to prevent intermittent connection pool exhaustion under high async query loads. The module currently exposes no configuration option for a maximum pool size.

Remote-SSH Connection Pool Size Change in VSCodium 1.96 Causes Intermittent Exhaustion

Investigating intermittent Remote‑SSH connection failures after VSCodium 1.96’s default pool size increase. Which pool threshold triggers errors, can a lower maxSize be a sustainable fix, and how to reliably apply the setting?

NetBeans JDBC Connection Pool Configuration Lacks Configurable Wait Timeout

NetBeans JDBC connection pool editor lacks a configurable wait‑timeout, causing possible UI hangs when the pool is exhausted; the unresolved decision is whether to expose this setting or rely on driver defaults.

Hibernate Pagination: Missing Default Page Size Constraint

Hibernate ORM 6.x lacks a documented default page size, risking unbounded result sets. Is a maximum default page size needed, how should it be configured, and what is the behavior with distinct projections and pagination?

GitLab database pool configuration: missing cross‑component limit enforcement

Goal

Constraints and uncertainty

0 answers

Your perspective belongs here.

0 question comments