From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Feature request: NOTIFY enhancement |
Date: | 2008-01-03 19:20:41 |
Message-ID: | 60ir2a7m2e.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
bruce(at)momjian(dot)us (Bruce Momjian) writes:
>> I am not sure if I am asking too much but does it make sense, and is it
>> possible, to enhance NOTIFY that process "name/value" pair? Like this:
>>
>> NOTIFY "MyName=MyValue";
>>
>> With the capability of name/value pair, the listener will not have to
>> check notification details by reading tables.
>
> TODO already has:
>
> * Add optional textual message to NOTIFY
>
> This would allow an informational message to be added to the notify
> message, perhaps indicating the row modified or other custom
> information.
I keep wondering if this isn't just going to grow into pgq...
<http://docs.huihoo.com/api/skytools/pgq-module.html>
In effect, once you start defining more semantics for this, I think it
rapidly transforms into a message queueing system, and you might as
well go straight to something full-fledged like pgq...
--
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://www3.sympatico.ca/cbbrowne/lisp.html
STATED REASON DOES NOT COMPUTE WITH PROGRAMMED FACTS...
From | Date | Subject | |
---|---|---|---|
Next Message | James B. Byrne | 2008-01-03 21:57:33 | CentOS-5 PostgreSQL 8.1.9 server instrumentation |
Previous Message | Bruce Momjian | 2008-01-03 18:47:56 | Re: Feature request: NOTIFY enhancement |