postgresql - Ignore/reconnect for closed connection in pool -


i have problem pool.acquire() , closed connection in pool. setting on pg server set connection timeout 120 second. when use pool.acquire() raise error because connection closed:

sleep 150 traceback (most recent call last):   file "test.py", line 21, in <module>     loop.run_until_complete(test_select())   file "/usr/local/cellar/python3/3.5.1/frameworks/python.framework/versions/3.5/lib/python3.5/asyncio/base_events.py", line 337, in run_until_complete     return future.result()   file "/usr/local/cellar/python3/3.5.1/frameworks/python.framework/versions/3.5/lib/python3.5/asyncio/futures.py", line 274, in result     raise self._exception   file "/usr/local/cellar/python3/3.5.1/frameworks/python.framework/versions/3.5/lib/python3.5/asyncio/tasks.py", line 239, in _step     result = coro.send(none)   file "test.py", line 10, in test_select async pool.acquire() conn:   file "/usr/local/lib/python3.5/site-packages/aiopg/utils.py", line 116, in __aenter__     self._conn = yield self._coro   file "/usr/local/lib/python3.5/site-packages/aiopg/pool.py", line 170, in _acquire     assert not conn.closed, conn assertionerror: <aiopg.connection.connection object @ 0x106f7df98>

and code

import asyncio import aiopg  dsn = 'dbname=dbname user=user password=password host=127.0.0.1' async def test_select():     async aiopg.create_pool(dsn) pool:         print("sleep 150")         await asyncio.sleep(150)         async pool.acquire() conn:             async conn.cursor() cur:                 await cur.execute("select 1")                 ret = []                 async row in cur:                     ret.append(row)                 assert ret == [(1,)]     print("all done")   loop = asyncio.get_event_loop() loop.run_until_complete(test_select())

how solve problem. thanks!


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more