diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-10-12 09:08:53 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-10-12 09:08:53 +0300 |
| commit | a1e664d4cc1edc8e5d6bd4a838e5e6a7426cc0f6 (patch) | |
| tree | 4d687e4149c7cbd2b3d01cdca370bd6aa9c7549f /doc/development/database/client_side_connection_pool.md | |
| parent | db4ee69eb3df58ac9f109d64228d1468e4ff7962 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/database/client_side_connection_pool.md')
| -rw-r--r-- | doc/development/database/client_side_connection_pool.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/development/database/client_side_connection_pool.md b/doc/development/database/client_side_connection_pool.md index b50e6b4f7a0..1a30d2d73a3 100644 --- a/doc/development/database/client_side_connection_pool.md +++ b/doc/development/database/client_side_connection_pool.md @@ -15,7 +15,6 @@ Because of the way [Ruby on Rails manages database connections](#connection-lifecycle), it is important that we have at least as many connections as we have threads. While there is a 'pool' setting in [`database.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/database.yml.postgresql), it is not very practical because you need to -maintain it in tandem with the number of application threads. Because maintain it in tandem with the number of application threads. For this reason, we override the number of allowed connections in the database connection-pool based on the configured number of application threads. |