If you are trying to get around the issue for now, what my team did was cron an insert statement on the database server. We have a queue table that has some of these triggers setup so it was easy to write a no-op row to the queue. This had the side effect of flushing the notification queue.
We haven't had any issues with this approach.
I can also volunteer to help test out patches.
Thanks,
-mdj
On Fri, Feb 22, 2019 at 11:37 AM Robert Welin <robert@vaion.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.
Regards,
Robert Welin
