On Wednesday, April 10, 2019 at 3:29:47 PM UTC-4, Mike Bayer wrote: > > The connection pool is safe in single process multiple threads. It breaks > on fork() because the socket travels across the process boundary and is > essentially copied between two or more processes that are unaware of each > other. >
Mike, I absolutely trust you on this and am accepting your statement as fact, but I have *somehow* had issues in the past running Pyramid in a threaded server without `dispose()`, which stopped once I invoked `dispose()`. I assumed it was because of that particular shared memory issue, but it must be elsewhere. -- 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.
