I have several programs that are Multi Process and long running, they
open up 30 or so connections and do selects periodically.
For a select query, the default behaviour is to begin a transaction if
not currently in one, but not commit afterwards. This leaves a large
number of postgresql processes with a status of "idle in transaction".
Which means they "lock" tables, so you can not drop them or alter them
including add and drop indexes. I have also seen some problems were
connections do not get closed if the connecting process exits, although
I haven’t verified this is the cause.
Is this a problem others have had in the past or am I just being overly
worried?
If it is a problem is there any other way to fix it beside commit()'ing
after each select query? I tried add an event handler after queries get
run, but I didn't see a way to get to the current transaction.
thanks
Ed
--
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 http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
