I've been looking into twisted.enterprise.. and I have a few questions It seems that enterprise expects that you want to commit data for every successful query? This certainly makes things simpler, as with PostgreSQL a separate backend (connection) is going to be running for every connection to that database, which means the thread pool would require some more complicated management. There ought to be a way to set it up such that your callbacks can do more processing and guarantee that it happens in the same thread, so you get the same connection, and don't have to commit every time. Committing after every query kinda defeats the purpose of having transactions at all, unless you do everything in user defined functions (stored procedures) that use transactions themselves. Similarly, what's the point of rolling back on error if you can't use transactions anyways? If it errored, it didn't do anything anyways. One more thing, do you need to do anything with threadable before using enterprise? -bob