| From: | Alan Kleiman <alan(dot)kleiman(at)ifood(dot)com(dot)br> |
|---|---|
| To: | "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-08-29 15:03:22 |
| Message-ID: | CAE6pZ52Cb+kb_RA_zHD-ptpE2nkBtQZJX=CfbxUd-_CXdEiLDw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Fri, Feb 22, 2019 at 11:37 AM Robert Welin <robert(at)vaion(dot)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.
>
> Same, I've reproduced this on 11.4 and 10.9. Are there any plans to
address this?
If there's nothing in the short-term, can we get a caveat in the
documentation for notify/logical
replication explaining this shortcoming?
--
Alan Kleiman
alan(dot)kleiman(at)ifood(dot)com(dot)br
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-08-29 15:48:46 | BUG #15984: order of where in() query affects query planer |
| Previous Message | Fabien COELHO | 2019-08-29 14:58:18 | Re: BUG #15977: Inconsistent behavior in chained transactions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2019-08-29 18:08:27 | Re: A problem about partitionwise join |
| Previous Message | Fabien COELHO | 2019-08-29 14:58:18 | Re: BUG #15977: Inconsistent behavior in chained transactions |