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 < >dan...@dd-wrt.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.
