summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/postgresql/asyncpg.py
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2021-06-26 09:55:00 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2021-06-26 09:55:00 -0400
commit3d6130d8e92dc3fd63e7192908e122fe5ee45699 (patch)
treed6bdbd3e64b0aa9063153a0ad38ac037694e8469 /lib/sqlalchemy/dialects/postgresql/asyncpg.py
parent791f1d9407f68cc668c7078fa87784ebdf3bd688 (diff)
downloadsqlalchemy-3d6130d8e92dc3fd63e7192908e122fe5ee45699.tar.gz
turn pg provision error into a warning
We haven't had any real cases of the PG "cant drop tables" condition since this error was first introduced; instead we seem to get it for a non-critical query during pool reconnect tests, and I have not been able to isolate what is causing it. Therefore turn the error into a new class of warning that can emit within the test suite without failing the test, so that if we do get a real PG drop timeout, the warning will be there to show us what the query was in which it was stuck. Change-Id: I1a9b3c4f7a25b7b9c1af722a721fc44ad5575b0f
Diffstat (limited to 'lib/sqlalchemy/dialects/postgresql/asyncpg.py')
0 files changed, 0 insertions, 0 deletions