From a326bfb395f7835ee68e6d24d3e2e90ce9e62cb1 Mon Sep 17 00:00:00 2001 From: Patrick Steinhardt Date: Tue, 24 May 2022 11:29:45 +0200 Subject: ci: Increase connection limit for Postgres We regularly get CI failures when running with Praefect, which is most likely caused by an exhaustion of the database's connection pool. Increase the limit so that we can hopefully get to a more stable state. Note that we cannot set `PGOPTIONS` here as that causes the Postgres services to not come up. Instead, we work around this by manually adding the configuration to the executed command. --- .gitlab-ci.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index c4c75e7e8..de8f216a3 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -77,7 +77,9 @@ include: - *cache_gems_configuration - *cache_go_configuration services: - - postgres:${POSTGRES_VERSION} + - name: postgres:${POSTGRES_VERSION} + alias: postgres + command: ["postgres", "-c", "max_connections=500"] variables: &postgres_variables PGHOST: postgres PGPORT: 5432 @@ -198,7 +200,9 @@ test:coverage: test:pgbouncer: <<: *test_definition services: - - postgres:${POSTGRES_VERSION} + - name: postgres:${POSTGRES_VERSION} + alias: postgres + command: ["postgres", "-c", "max_connections=500"] - name: bitnami/pgbouncer:${PGBOUNCER_VERSION} alias: pgbouncer variables: -- cgit v1.2.3