You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PostgreSQL version: PostgreSQL 9.6.6 on x86_64-pc-linux-musl, compiled by gcc (Alpine 6.2.1) 6.2.1 20160822, 64-bit and PostgreSQL 9.5
Do you use a PostgreSQL SaaS? If so, which? Can you reproduce
the issue with a local PostgreSQL install?: Yes, I can reproduce. AWS and local
Python version: 3.6.6
Platform: Linux
Do you use pgbouncer?: no
Did you install asyncpg with pip?: yes
If you built asyncpg locally, which version of Cython did you use?: no
Can the issue be reproduced under both asyncio and uvloop?: didn't try using uvloop
When a connection from a pool is killed from database (asyncpg.exceptions.ConnectionDoesNotExistError), the pool cannot recovery this connection and the pool size will be compromised, reaching zero connections available even though no queries are executing.
This can happen other ways besides the ConnectionDoesNotExistError exception.
The following code can be used to reproduce this issue.
the issue with a local PostgreSQL install?: Yes, I can reproduce. AWS and local
uvloop?: didn't try using uvloop
When a connection from a pool is killed from database (asyncpg.exceptions.ConnectionDoesNotExistError), the pool cannot recovery this connection and the pool size will be compromised, reaching zero connections available even though no queries are executing.
This can happen other ways besides the ConnectionDoesNotExistError exception.
The following code can be used to reproduce this issue.
The text was updated successfully, but these errors were encountered: