Date: Fri, 28 Jun 2019 17:22:24 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: 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>
Subject: Re: BUG #15293: Stored Procedure Triggered by Logical Replication is
 Unable to use Notification Events
Message-ID: <20190628212224.GA11418@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1788fd6f-308a-77e7-ef82-a2325f506ed6@vaion.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

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 :-(

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services