From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Arnaud Betremieux <arnaud(dot)betremieux(at)keyconsulting(dot)fr>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Cyrille Chépélov <cyrille(dot)chepelov(at)keyconsulting(dot)fr>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Listen / Notify - what to do when the queue is full |
Date: | 2010-01-11 13:51:24 |
Message-ID: | b42b73151001110551p5052badfrd5239ede37b44ae3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 11, 2010 at 8:25 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> I'm working on a proof of concept patch to use Joachim's new notify
>> function to introduce case 3. I think this means going through the
>> planner and executor, so I might as well do case 4 as well.
>
> It would be a lot less work to introduce a function like send_notify()
> that could be invoked within a regular SELECT. Pushing a utility
+1
IMO, this neatly solves the problem and addresses some of the concerns
I was raising upthread. A bytea version would be nice but a text only
version is workable.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Abhijit Menon-Sen | 2010-01-11 14:00:03 | Re: mailing list archiver chewing patches |
Previous Message | Dimitri Fontaine | 2010-01-11 13:50:36 | Re: mailing list archiver chewing patches |