Re: Problem with psycopg2 and asyncio - Mailing list psycopg

From Frank Millman
Subject Re: Problem with psycopg2 and asyncio
Date
Msg-id B721C07E00FE407DB1729AE82183B405@FrankLaptop
Whole thread Raw
In response to Re: Problem with psycopg2 and asyncio  ("Frank Millman" <frank@chagford.com>)
Responses Re: Problem with psycopg2 and asyncio
List psycopg
On 02/03/16 09:48, Frank Millman wrote:
 
>
> It boils down to the fact that psycopg running in one thread is blocking another thread from executing. Running pyodbc and sqlite3 in exactly the same conditions do not have this effect. > Therefore my (quite possibly wrong) suspicion is that the GIL is not being released timeously, or at least psycopg is doing something different from the others.
>
 
It occurs to me that there is one difference which could be significant. As far as I know, pyodbc and sqlite do not use sockets to communicate with the database, but psycopg does. Whether that could interfere with the socket-handling in the asyncio thread I have no idea, but it is a possibility.
 
Frank
 

psycopg by date:

Previous
From: "Frank Millman"
Date:
Subject: Re: Problem with psycopg2 and asyncio
Next
From: Federico Di Gregorio
Date:
Subject: Re: Problem with psycopg2 and asyncio