From: | Jan Urbański <wulczer(at)wulczer(dot)org> |
---|---|
To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
Cc: | Tobias Oberstein <tobias(dot)oberstein(at)tavendo(dot)de>, "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org> |
Subject: | Re: NOTIFY in asynchronous mode |
Date: | 2011-11-05 00:03:53 |
Message-ID: | 4EB47D69.3050808@wulczer.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On 04/11/11 21:23, Daniele Varrazzo wrote:
> On Fri, Nov 4, 2011 at 7:12 PM, Tobias Oberstein
> <tobias(dot)oberstein(at)tavendo(dot)de> wrote:
>
>> is it possible to use notification (sent via NOTIFY from Postgres) in asynchronous mode?
>
> Yes: you should register the connection's file descriptor in the
> twisted reactor so that you can be notified by the kernel when the
> server sends you a notification.
Actually... it won't work out of the box. I got a patch from someone
that added NOTIFY support for txpostgres, but it broke some unit tests
and there were a few other minor issues with it and then I kind of
forgot about it.
Recently I've been picking up txpostgres' development and I might add
NOTIFY support soon, maybe even the next week.
The problem with it now is that when there's no query going on, the
connection's descriptor is not present in the reactor, it only gets
added for the duration of the query. Once I figure out how to change
that without breaking some subtle corner cases, you'll be able to
register a NOTIFY callback that will get called when there's an async
notification received by the connection.
Cheers,
Jan
From | Date | Subject | |
---|---|---|---|
Next Message | Daniele Varrazzo | 2011-11-05 00:15:30 | Re: NOTIFY in asynchronous mode |
Previous Message | Daniele Varrazzo | 2011-11-04 20:23:33 | Re: NOTIFY in asynchronous mode |