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

From: Robert Welin <robert(at)vaion(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Sergei Kornilov <sk(at)zsrv(dot)org>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, Marc Dean <marc(dot)dean(dot)jr(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, "michael(dot)paul(dot)powers(at)gmail(dot)com" <michael(dot)paul(dot)powers(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events
Date: 2019-02-22 16:37:50
Message-ID: 1788fd6f-308a-77e7-ef82-a2325f506ed6@vaion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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.

Regards,
Robert Welin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-02-22 17:16:57 BUG #15652: PG Admin 4 - Find and Replace
Previous Message PG Bug reporting form 2019-02-22 16:34:43 BUG #15651: Collation setting en_US.utf8 breaking sort order

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2019-02-22 16:49:49 Re: Autovaccuum vs temp tables crash
Previous Message Stephen Frost 2019-02-22 16:32:41 Re: Remove Deprecated Exclusive Backup Mode