itest: increase pg database connection limit

This commit is contained in:
Joost Jager 2021-12-27 09:36:51 +01:00
parent 71ecc8a299
commit 2009aec59d
No known key found for this signature in database
GPG Key ID: A61B9D4C393C59C7
2 changed files with 6 additions and 3 deletions

View File

@ -177,9 +177,10 @@ ifeq ($(dbbackend),postgres)
# Remove a previous postgres instance if it exists.
docker rm lnd-postgres --force || echo "Starting new postgres container"
# Start a fresh postgres instance. Allow a maximum of 500 connections.
# This is required for the async benchmark to pass.
docker run --name lnd-postgres -e POSTGRES_PASSWORD=postgres -p 6432:5432 -d postgres:13-alpine
# Start a fresh postgres instance. Allow a maximum of 500 connections so
# that multiple lnd instances with a maximum number of connections of 50
# 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 &
# Wait for the instance to be started.

View File

@ -50,6 +50,8 @@
led to an already made connection being lost. [This is now fixed so that
bootstrapping will always ignore the peers chosen by the persistent
connection.](https://github.com/lightningnetwork/lnd/pull/6082)
* [Fix Postgres itests max connections](https://github.com/lightningnetwork/lnd/pull/6116)
## RPC Server