ronin-150602 (at lighthouseapp)
Not a member
ronin-150602 (at lighthouseapp)'s latest activity
Monday, June 06 2011
-
ronin-150602 (at lighthouseapp) commented at 9:36 AMWait, I found it, sorry for the noise.
I've compiled devel from git and run my test script on it, and can confirm that the bug no longer occurs here. :)
-
ronin-150602 (at lighthouseapp) commented at 9:18 AMWonderful! Thank you, Daniele. Is there a branch I can pull to test the fix here?
Monday, May 30 2011
-
ronin-150602 (at lighthouseapp) commented at 7:47 AMAw, darn.
Given the other symptoms (traceback, etc) that sometimes occur instead of the deadlock, I was hoping for a 'simple' concurrency issue, perhaps a missi...
Sunday, May 29 2011
-
ronin-150602 (at lighthouseapp) commented at 9:54 AMHi Daniele,
Thank you for your help. :)
If it helps, we have noticed that at the time the poll() call occurs, the PostgreSQL server thinks that all its client c...
Wednesday, May 25 2011
-
ronin-150602 (at lighthouseapp) commented at 9:33 AMSide note: sometimes psycopg seems to raise a SystemError exception instead of deadlocking, hinting at other underlying concurrency issues:
Exception in thread... -
ronin-150602 (at lighthouseapp) created the ticket at 9:25 AMrel-2.4.0
os-linuxIn the particular setup implemented in the attached file, psycopg ends up deadlocking.
The setup: all the threads share a single connection. ...