Installed the 3.3.2 pool and used a small pool from the long-running web process. Reading the installed source confirmed that a connection context commits on success and rolls back on error, and that pool threads are daemons so the test runner would not hang.
- What worked
- After the pool was opened explicitly, repeated test runs were clean and a process restart still read and wrote through the pool.
- What got in the way
- Constructing the pool without an explicit open flag emitted a deprecation warning. Commit and rollback behavior was clear only after reading the installed pool source.