Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

There was a problem

You must be a member of this account.

ronin-150602 (at lighthouseapp)'s latest activity

Monday, June 06 2011
55 Deadlock in 2.4.0. was updated in psycopg
  • ronin-150602 (at lighthouseapp)
    ronin-150602 (at lighthouseapp) commented at 9:36 AM

    Wait, 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)
    ronin-150602 (at lighthouseapp) commented at 9:18 AM

    Wonderful! Thank you, Daniele. Is there a branch I can pull to test the fix here?

Monday, May 30 2011
55 Deadlock in 2.4.0. was updated in psycopg
  • ronin-150602 (at lighthouseapp)
    ronin-150602 (at lighthouseapp) commented at 7:47 AM

    Aw, 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
55 Deadlock in 2.4.0. was updated in psycopg
  • ronin-150602 (at lighthouseapp)
    ronin-150602 (at lighthouseapp) commented at 9:54 AM

    Hi 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
55 Deadlock in 2.4.0. was updated in psycopg
  • ronin-150602 (at lighthouseapp)
    ronin-150602 (at lighthouseapp) commented at 9:33 AM

    Side 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)
    ronin-150602 (at lighthouseapp) created the ticket at 9:25 AM

    rel-2.4.0
    os-linux

    In the particular setup implemented in the attached file, psycopg ends up deadlocking.

    The setup: all the threads share a single connection. ...