| From: | Sergey Fedchenko <seregayoga(at)bk(dot)ru> |
|---|---|
| To: | Daniel Danzberger <daniel(at)dd-wrt(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sergei Kornilov <sk(at)zsrv(dot)org>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, Marc Dean <marc(dot)dean(dot)jr(at)gmail(dot)com>, 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>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Welin <robert(at)vaion(dot)com> |
| Subject: | Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events |
| Date: | 2021-06-14 11:17:24 |
| Message-ID: | 1623669444.237579337@f317.i.mail.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hi all! I still can reproduce it on 14beta1 version. I adapted a patch I found in this thread https://github.com/seregayoga/postgres/commit/338bc33f2cf77edde7c45bfdfb9f39a92ec57eb8 . It solved this bug for me (tested with simple Go program using https://github.com/lib/pq ). It would be nice to have this bug fixed. I’m not so familiar with postgres code base, but would glad to help with testing.
>Monday, June 14, 2021 12:39 PM +03:00 from Daniel Danzberger < daniel(at)dd-wrt(dot)com >:
>
>On Fri, 2019-06-28 at 17:22 -0400, Alvaro Herrera wrote:
>> On 2019-Feb-22, Robert Welin 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.
>>
>> This issue seems largely forgotten about :-(
>>
>Are there any news to this issue ?
>I can reproduce this bug up to now with version 12.
>
>--
>Regards
>
>Daniel Danzberger
>embeDD GmbH, Alter Postplatz 2, CH-6370 Stans
>
>
>
>
Best regards, Sergey Fedchenko.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-06-14 11:33:39 | Fwd: BUG #17056: Segmentation fault on altering the type of the foreign table column with a default |
| Previous Message | Thomas Munro | 2021-06-13 20:33:05 | Re: BUG #17058: Unable to create collation in version 13. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-06-14 11:33:39 | Fwd: BUG #17056: Segmentation fault on altering the type of the foreign table column with a default |
| Previous Message | John Naylor | 2021-06-14 11:16:58 | Re: a path towards replacing GEQO with something better |