| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu>, Andrew Chernow <ac(at)esilo(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Joachim Wieland <joe(at)mcknight(dot)de>, 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:06:23 |
| Message-ID: | 4FC454CAD5156EF6779EB70B@amenophis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On 12. November 2009 15:48:44 +0000 Greg Stark <gsstark(at)mit(dot)edu> wrote:
> I'm beginning to think the right solution is to reject the idea of
> adding a payload to the NOTIFY mechanism and instead provide a queue
> contrib module which provides the interface people want.
Isn't PgQ already the solution you have in mind?
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-11-12 16:13:07 | plpgsql GUC variable: custom or built-in? |
| Previous Message | Joachim Wieland | 2009-11-12 16:00:07 | Re: Listen / Notify rewrite |