idle in transaction about relstorage HOT 10 CLOSED

transactions are not closed after read but kept open unless a write happens. This is not critical, but as far as i understand its also not clean.

from relstorage.

https://mail.zope.org/pipermail/zodb-dev/2014-March/015198.html

from relstorage.

Duplicate of #7

from relstorage.

Also, if you are using RelStorage 1.5.0 or older, this might be a problem that was fixed in 1.5.1 (November 2011). From the changelog: "RelStorage was opening a test database connection (and was leaving it idle in a transaction with recent ZODB versions that support IMVCCStorage.) RelStorage no longer opens that test connection."

from relstorage.

No, it is related to this:

from relstorage.

The poll interval option is off by default. Don't turn it on if this is a concern for you. Actually, perhaps the option should be removed altogether.

from relstorage.

So I need to check why some of my 1.6.0b3 instances with no poll interval set (defaults active) are resulting in idle in transaction on PGSQL.

from relstorage.

I also tried it yesterday, with 1.5.1. Poll Intervall 0, still immed. Idle transactions.

Sent from my iPhone because UPC sucks

On 05 Dec 2015, at 21:26, Jens W. Klein <[email protected]mailto:[email protected]> wrote:

So I need to check why some of my 1.6.0b3 instances with no poll interval set (defaults active) are resulting in idle in transaction on PGSQL.

Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-162243403.

________________________________________________________ The contents of this e-mail and any attachments are confidential to the intended recipient. They may not be disclosed to or used by or copied in any way by anyone other than the intended recipient. If this e-mail is received in error, please immediately notify the sender and delete the e-mail and attached documents. Please note that neither the sender nor the sender's company accept any responsibility for viruses and it is your responsibility to scan or otherwise check this e-mail and any attachments.

from relstorage.

Postgres 9.6 has a new option , idle transaction timeout. This blogpost https://www.credativ.de/blog/postgresql-96-feature-idle-transaction-timeout (german) also explains the downsides of having idle transactions open. We are currently in maintenance mode with our big system using Relstorage. @jensens, are you actively working on some psql site where you can test this option to see if it makes a difference?

from relstorage.

FWIW, the poll interval option has been removed in RelStorage 2.0.

from relstorage.