Re: psycopg2 hang with multithread frequent queries - Mailing list psycopg

From David Roid
Subject Re: psycopg2 hang with multithread frequent queries
Date
Msg-id CAKN1bq4Uu2rNpT5FuDZ_Ouf+y+QhODw45Op6aX5i7PiSfWom7A@mail.gmail.com
Whole thread Raw
In response to Re: psycopg2 hang with multithread frequent queries  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
List psycopg
Thank you, I'll do some homework on gevent.

-David

2012/9/18 Daniele Varrazzo <daniele.varrazzo@gmail.com>
On Tue, Sep 18, 2012 at 12:39 AM, P. Christeas <xrg@linux.gr> wrote:
> On Tuesday 18 September 2012, David Roid wrote:
>> Hi Daniele, Federico,
>>
>> Just want to know, if I keep signal handler but switch from thread to
>> subprocess, i.e. put the signal handler code with database queries into
>> another process, is that safe?
>>
>
> IMHO, doing anything more than setting some "flag" variables and waking up
> regular threads is bad practice for a signal handler..

Yeah, in a process handler you are not even supposed to call malloc.
This on top of the fact that in python interaction between threads and
signals is unpredictable.

If you want more refined synchronization across agents you may take a
look at gevent/eventlet. But without knowing your problem is hard to
guess a solution.

-- Daniele


--
Sent via psycopg mailing list (psycopg@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/psycopg

psycopg by date:

Previous
From: Daniele Varrazzo
Date:
Subject: Re: psycopg2 hang with multithread frequent queries
Next
From: Tobias Oberstein
Date:
Subject: JSON type caster