From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, jacques klein <jacques(dot)klei(at)googlemail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: NOTIFY in Background Worker |
Date: | 2015-11-06 04:46:27 |
Message-ID: | CAEepm=2h8_-o_FERHJJbAbGACZggOJ0BUDn0=_ygb_Ggwne9Zg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 6, 2015 at 12:08 PM, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
wrote:
> On Fri, Nov 6, 2015 at 4:57 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > On Thu, Nov 5, 2015 at 12:34 AM, Haribabu Kommi
> > <kommi(dot)haribabu(at)gmail(dot)com> wrote:
> >> I marked this patch as ready for committer.
> >
> > The patch says:
> >
> > If a background worker registers to receive asynchronous notifications
> > with the <command>LISTEN</command> through <acronym>SPI</acronym>,
> > there is currently no way for incoming notifications to be received.
> >
> > But wouldn't it be more correct to say:
> >
> > If a background worker registers to receive asynchronous notifications
> > with the <command>LISTEN</command> through <acronym>SPI</acronym>, the
> > worker will log those notifications, but there is no programmatic way
> > for the worker to intercept and respond to those notifications.
>
> Yes, the above description is good.
+1
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-11-06 04:47:20 | Re: Within CF app, "Bug Fixes" should be "Bug Fixes/Refactoring" |
Previous Message | Robert Haas | 2015-11-06 04:45:53 | Re: Some questions about the array. |