Does anyone here know if DBD::Pg starts a new transaction after a COMMIT? That is, it appears that...
$dbh->do(...); $dbh->commit(...); # End of one transaction # Code here will have an implicit 'BEGIN' If this is the case, it would explain some performance problems we are having. We have some detached processes running as daemons with open database handles. We get a lot of these messages: NOTICE: InvalidateSharedInvalid: cache state reset which I'm told implies that we have a lot of "idle in transaction" processes. If all this is true, how do I fix it? Must my idle daemons release their database handles? What about mod_perl processes? -- Jeff Boes vox 616.226.9550 Database Engineer fax 616.349.9076 Nexcerpt, Inc. [EMAIL PROTECTED]
