Re: Listen / Notify rewrite - Mailing list pgsql-hackers

From Andrew Chernow
Subject Re: Listen / Notify rewrite
Date
Msg-id 4AFC3648.1050008@esilo.com
Whole thread Raw
In response to Re: Listen / Notify rewrite  (Joachim Wieland <joe@mcknight.de>)
Responses Re: Listen / Notify rewrite
List pgsql-hackers
> However I share Greg's concerns that people are trying to use NOTIFY
> as a message queue which it is not designed to be.

When you have an established libpq connection waiting for notifies it is 
not unreasonable to expect/desire a payload.  ISTM, the problem is that 
the initial design was half-baked.  NOTIFY is event-driven, ie. no 
polling!

-- 
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: array_to_string bug?
Next
From: Robert Haas
Date:
Subject: Re: plpgsql GUC variable: custom or built-in?