| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org>, Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Cc: | "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 15:58:29 |
| Message-ID: | 20180724155829.zq22vov6d7erhxsx@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hi,
On 2018-07-24 16:19:45 +0300, Sergei Kornilov wrote:
> I checked this bug and found reason: we do not notify backends about new events by call ProcessCompletedNotifies from logical worker.
> New notify from regular backend does call ProcessCompletedNotifies: send signal to all listen backends and found new events for youself.
> But i am not sure where is correct place for call ProcessCompletedNotifies in logical worker src/backend/replication/logical/worker.c and i can not provide patch.
Peter, Petr, this is the second report of this issue. Anything?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Dean | 2018-07-24 17:43:30 | Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events |
| Previous Message | Tom Lane | 2018-07-24 13:54:14 | Re: BUG #15292: Multiple Messages "2018-07-24 10:46:12.566 CEST [32029] LOG: invalid length of startup" in logfile |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-07-24 16:18:44 | Re: Stored procedures and out parameters |
| Previous Message | Dave Cramer | 2018-07-24 15:52:12 | Reviving the "Stopping logical replication protocol" patch from Vladimir Gordichuk |