Horton

Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events

Alan Kleiman <alan.kleiman@ifood.com.br>

View thread View on postgr.es
From: Alan Kleiman <alan.kleiman@ifood.com.br>
To: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2019-08-29T15:03:22Z
Lists: pgsql-bugs, pgsql-hackers 
On Fri, Feb 22, 2019 at 11:37 AM Robert Welin <robert(at)vaion(dot)com>
wrote:

> I have reproduced this bug on PostgreSQL version 10.7 and 11.2 using the
> steps described in Michael Powers' original report. The issue also still
> seems to be present even with the patch provided by Sergei Kornilov.
>
> Are there plans to address this issue any time soon or is there some way
> I can assist in fixing it? It would be great to have notifications from
> logical replication.
>
> Same, I've reproduced this on 11.4 and 10.9. Are there any plans to
address this?
If there's nothing in the short-term, can we get a caveat in the
documentation for notify/logical
replication explaining this shortcoming?


-- 
Alan Kleiman
alan.kleiman@ifood.com.br

Commits

  1. Disallow LISTEN in background workers.

  2. Send NOTIFY signals during CommitTransaction.

  3. Make some efficiency improvements in LISTEN/NOTIFY.