| From: | Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | fabio(dot)vianello(at)salvagninigroup(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16481: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events |
| Date: | 2020-06-08 10:51:18 |
| Message-ID: | CAH503wAro5n_6o3bE3Xmij88Xoan4d_ytjG7rc=UX+NVE-dHFw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, 8 Jun 2020 at 05:27, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
wrote:
>
> That can be fixed by calling ProcessCompletedNotifies() in
> apply_handle_commit. The function has a code to write out
> notifications to connected clients but it doesn't nothing on logical
> replication workers.
>
>
This bug was already reported some time ago (#15293) but it slipped through
the
cracks. I don't think you should simply call ProcessCompletedNotifies [1].
[1] https://www.postgresql.org/message-id/13844.1532468610%40sss.pgh.pa.us
--
Euler Taveira http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-06-08 17:37:07 | Re: |
| Previous Message | Vianello Fabio | 2020-06-08 09:13:44 | RE: BUG #16481: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey Kondratov | 2020-06-08 11:16:32 | Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line |
| Previous Message | amul sul | 2020-06-08 10:44:53 | Re: race condition when writing pg_control |