Re: Listen / Notify rewrite

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Joachim Wieland <joe(at)mcknight(dot)de>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Andrew Chernow <andrew(at)esilo(dot)com>
Subject: Re: Listen / Notify rewrite
Date: 2009-11-12 16:22:32
Message-ID: 4AFC3648.1050008@esilo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-11-12 16:26:23 Re: plpgsql GUC variable: custom or built-in?
Previous Message Tom Lane 2009-11-12 16:20:26 Re: array_to_string bug?