From a1e664d4cc1edc8e5d6bd4a838e5e6a7426cc0f6 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Mon, 12 Oct 2020 06:08:53 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/development/database/client_side_connection_pool.md | 1 - 1 file changed, 1 deletion(-) (limited to 'doc/development/database/client_side_connection_pool.md') 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. -- cgit v1.2.3