On Thu, Jul 17, 2014 at 2:37 PM, Leonardo Rochael Almeida
wrote:
> I seem to recall, though I couldn't find references to it now, that this
> could happen if there is a firewall between the RelStorage using
> processes/threads and your database.
>
> If a long time passes without any activity, this
I have implemented commit-lock-timeout for PostgreSQL 9.3+ in a fork on github.
See:
https://github.com/upiq/relstorage/commit/6ac7bf31ce3491ff87f5c138c892c0c0906c12ac
However, I am unclear though what the effect of using the default 30
second lock timeout is for transactions that take a long
I seem to recall, though I couldn't find references to it now, that this
could happen if there is a firewall between the RelStorage using
processes/threads and your database.
If a long time passes without any activity, this could cause the firewall
to forget about the long lived TCP connections th
