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

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: Marc Dean <marc(dot)dean(dot)jr(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: 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: 2018-07-24 18:22:18
Message-ID: 648481532456538@myt5-0fa3e541b8b9.qloud-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Hello
in fact, I've already tried to build fix. Adding ProcessCompletedNotifies to apply_handle_commit fixed this issue and i think this is right place. In src/backend/tcop/postgres.c we call ProcessCompletedNotifies similar way after commit. This change pass make check-world.
So i attach my two line patch.

regards, Sergei

Attachment Content-Type Size
bug15293.patch text/x-diff 668 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-07-24 19:14:52 BUG #15294: Phantom read in serializable transaction when you rename schema.
Previous Message Marc Dean 2018-07-24 17:43:30 Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Verite 2018-07-24 18:31:39 Re: Stored procedures and out parameters
Previous Message Marc Dean 2018-07-24 17:43:30 Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events