Can you share/show how/where they engines and connections are created? This is odd.
FWIW, with the forking bug- the issue isn't in the transaction/session but in the underlying database connections. The SqlAlchemy connection pool isn't threadsafe, so all the commits/rollbacks/etc in different sessions/transactions made in different sessions end up happening on the same connection. On Friday, June 22, 2018 at 8:18:51 PM UTC-4, HP3 wrote: > > No dice! > > I verified that engines and sessions are created after fork. > > By hijacking celery logging, verified each worker had its own transaction > and session. > > The SQL logs I described above are indeed accurate and belong to the same > worker. > -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
