| From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
|---|---|
| To: | Frank Millman <frank(at)chagford(dot)com> |
| Cc: | "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org> |
| Subject: | Re: Problem with psycopg2 and asyncio |
| Date: | 2016-03-01 15:30:14 |
| Message-ID: | CA+mi_8YxUkWBemjkhYT1UQgAaH+4D5emnYX+jgg6G3cJRdMD6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
On Tue, Mar 1, 2016 at 5:24 AM, Frank Millman <frank(at)chagford(dot)com> wrote:
> On 29/02/16 18:07, Daniele Varrazzo wrote:
>>
>> On Mon, Feb 29, 2016 at 2:52 PM, Frank Millman <frank(at)chagford(dot)com> wrote:
>>
>> > Of course I may just be doing something silly, in which case I would be
>> > delighted if someone pointed it out.
>>
>> Are you running psycopg in async mode or in green mode?
>>
> To be honest, I don’t know what that means, so I am probably running in
> green mode.
I think you should have that under control if you want psycopg to
perform ok in asynchronous environment.
Call psycopg2.extensions.get_wait_callback(). If it returns None, then
psycopg is simply blocking.
-- Daniele
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Millman | 2016-03-02 07:48:30 | Re: Problem with psycopg2 and asyncio |
| Previous Message | Frank Millman | 2016-03-01 05:24:10 | Re: Problem with psycopg2 and asyncio |