Closing connection object throws exception about aiopg HOT 8 CLOSED

Got it.

from aiopg.

We are also facing this issue, can you please patch this. We don't specify a timeout value though.

Specifically for us it occurs when we pass a 'sub-query' to cursor.execute

from aiopg.

What do you mean by sub-query?
cusor object is intended to execute only one query in the same time.

from aiopg.

http://www.postgresql.org/docs/8.2/static/functions-subquery.html

from aiopg.

Changing this from a ProgrammingError to a TimeoutError seems to have been done in 8ca948e, which also makes sure the connection and cursor are closed when it happens. Can this issue be closed?

from aiopg.

Not yet. I should fix closing cursor with pending query first.
Will do it next week -- just after making new aiohttp release.

from aiopg.

Do we have any estimate for the fix? If sub-query is hard to implement, I think we should include the initial problem as soonn as possible. Because currently this blocks one from implementing a retry policy on specific DB errors. e.g: retry query on TimeOut Error 2 times.

from aiopg.

Fixed, d0e5f86 has explicit test for the issue

from aiopg.