pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Sergey Fedchenko <seregayoga@bk.ru>
To: Daniel Danzberger <daniel@dd-wrt.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sergei Kornilov <sk@zsrv.org>
Cc: pgsql-hackers@postgresql.org, Peter Eisentraut <peter_e@gmx.net>
Cc: Marc Dean <marc.dean.jr@gmail.com>
Cc: Petr Jelinek <petr@2ndquadrant.com>
Cc: michael.paul.powers@gmail.com <michael.paul.powers@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Robert Welin <robert@vaion.com>
Subject:  Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events
Date: Mon, 14 Jun 2021 14:17:24 +0300
Message-ID: <1623669444.237579337@f317.i.mail.ru> (raw)
In-Reply-To: <923262c473b494c4aec825a360d6f0499c144552.camel@dd-wrt.com>
References: <20190628212224.GA11418@alvherre.pgsql>
	<923262c473b494c4aec825a360d6f0499c144552.camel@dd-wrt.com>


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@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.
 
 

view thread (25+ messages)  latest in thread

Message-ID: <1623669444.237579337@f317.i.mail.ru>
Permalink:  ../1623669444.237579337@f317.i.mail.ru/
Also on:    postgresql.org/message-id/1623669444.237579337@f317.i.mail.ru

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: seregayoga@bk.ru, daniel@dd-wrt.com, andres@anarazel.de, tgl@sss.pgh.pa.us, sk@zsrv.org, peter_e@gmx.net, marc.dean.jr@gmail.com, petr@2ndquadrant.com, michael.paul.powers@gmail.com, pgsql-bugs@lists.postgresql.org, alvherre@2ndquadrant.com, robert@vaion.com
  Subject: Re:  Re: BUG #15293: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events
  In-Reply-To: <1623669444.237579337@f317.i.mail.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox