Re: NOTIFY in Background Worker - Mailing list pgsql-hackers

From Robert Haas
Subject Re: NOTIFY in Background Worker
Date
Msg-id CA+TgmoYW89ZBJwdSxUiH_n6bXixs-xEhK4ryTq50h9sJNEi=Lw@mail.gmail.com
Whole thread Raw
In response to Re: NOTIFY in Background Worker  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses Re: NOTIFY in Background Worker  (Haribabu Kommi <kommi.haribabu@gmail.com>)
List pgsql-hackers
On Thu, Nov 5, 2015 at 12:34 AM, Haribabu Kommi
<kommi.haribabu@gmail.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.

Or something like that?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Bitmap index scans use of filters on available columns
Next
From: Merlin Moncure
Date:
Subject: Re: Request: pg_cancel_backend variant that handles 'idle in transaction' sessions