Message-ID: <923262c473b494c4aec825a360d6f0499c144552.camel@dd-wrt.com>
From: Daniel Danzberger <daniel@dd-wrt.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>, Robert Welin
 <robert@vaion.com>
Cc: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Sergei
 Kornilov <sk@zsrv.org>, pgsql-hackers@postgresql.org, Peter Eisentraut
 <peter_e@gmx.net>, Marc Dean <marc.dean.jr@gmail.com>, Petr Jelinek
 <petr@2ndquadrant.com>,  "michael.paul.powers@gmail.com"
 <michael.paul.powers@gmail.com>, "pgsql-bugs@lists.postgresql.org"
 <pgsql-bugs@lists.postgresql.org>
Date: Tue, 23 Jun 2020 11:40:53 +0200
In-Reply-To: <20190628212224.GA11418@alvherre.pgsql>
References: <20190628212224.GA11418@alvherre.pgsql>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.3-1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: BUG #15293: Stored Procedure Triggered by Logical Replication
 is Unable to use Notification Events
Precedence: bulk

On Fri, 2019-06-28 at 17:22 -0400, Alvaro Herrera wrote:
> On 2019-Feb-22, Robert Welin 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.
> 
> This issue seems largely forgotten about :-(
> 

Are there any news to this issue ?
I can reproduce this bug up to now with version 12.

-- 
Regards

Daniel Danzberger
embeDD GmbH, Alter Postplatz 2, CH-6370 Stans