itest: increase pg database connection limit

This commit is contained in:
Joost Jager committed 2022-01-04 08:29:22 +01:00
1 parent 71ecc8a299
commit 2009aec59d
2 files changed
+6 -3

No files matched your search

+4 -3
View File
@@ -177,9 +177,10 @@ ifeq ($(dbbackend),postgres)
# Remove a previous postgres instance if it exists. # Remove a previous postgres instance if it exists.
docker rm lnd-postgres --force || echo "Starting new postgres container" docker rm lnd-postgres --force || echo "Starting new postgres container"
# Start a fresh postgres instance. Allow a maximum of 500 connections. # Start a fresh postgres instance. Allow a maximum of 500 connections so
# This is required for the async benchmark to pass. # that multiple lnd instances with a maximum number of connections of 50
docker run --name lnd-postgres -e POSTGRES_PASSWORD=postgres -p 6432:5432 -d postgres:13-alpine # each can run concurrently.
docker run --name lnd-postgres -e POSTGRES_PASSWORD=postgres -p 6432:5432 -d postgres:13-alpine -N 500
docker logs -f lnd-postgres & docker logs -f lnd-postgres &
# Wait for the instance to be started. # Wait for the instance to be started.
@@ -50,6 +50,8 @@
led to an already made connection being lost. [This is now fixed so that led to an already made connection being lost. [This is now fixed so that
bootstrapping will always ignore the peers chosen by the persistent bootstrapping will always ignore the peers chosen by the persistent
connection.](https://github.com/lightningnetwork/lnd/pull/6082) connection.](https://github.com/lightningnetwork/lnd/pull/6082)
* [Fix Postgres itests max connections](https://github.com/lightningnetwork/lnd/pull/6116)
## RPC Server ## RPC Server