…db state
Observed when running migration tests, that if should_run touches the database (even just reading, and even returning nothing), and subsequent migrations use the super_user cursor, they stall waiting on an "idle in transaction" connection that ran the should_run test code. For some reason, this only happens when running under python3.
Adding this savepoint/rollback to pair fixes the observed problem.
Further thought/discussion about the role of transactions and dbmigrator migrations is probably needed.
Coverage increased (+0.008%) to 97.126% when pulling 74148087adf981ae67bf39778a130645cfb90872 on Connexions:should-run-rollback into 78a3d3f13ffd5dc9aa41b8481a2d477d603f71ea on karenc:master.
…db state Observed when running migration tests, that if should_run touches the database (even just reading, and even returning nothing), and subsequent migrations use the super_user cursor, they stall waiting on an "idle in transaction" connection that ran the should_run test code. For some reason, this only happens when running under python3.
Adding this savepoint/rollback to pair fixes the observed problem.
Further thought/discussion about the role of transactions and dbmigrator migrations is probably needed.