RE: BUG #16481: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events

From: Vianello Fabio <fabio(dot)vianello(at)salvagninigroup(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com>
Subject: RE: BUG #16481: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events
Date: 2020-06-10 06:02:54
Message-ID: AM6PR06MB61683FC942E91A3AC184DF1E93830@AM6PR06MB6168.eurprd06.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

I think you did follow all the thread. I only ask if it is a bug or not. If it as bug and last for years I understand your point our view but I have my.

If you think that signal a bug is not give a contribution I am astonished.

Improve PosgreSQL is the target!!!!

Best Regard.

Fabio Vianello.

From: David G. Johnston [mailto:david(dot)g(dot)johnston(at)gmail(dot)com]
Sent: martedì 9 giugno 2020 17:10
To: Vianello Fabio <fabio(dot)vianello(at)salvagninigroup(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>; pgsql-bugs(at)lists(dot)postgresql(dot)org; Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>; Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com>
Subject: Re: BUG #16481: Stored Procedure Triggered by Logical Replication is Unable to use Notification Events

On Tue, Jun 9, 2020 at 12:36 AM Vianello Fabio <fabio(dot)vianello(at)salvagninigroup(dot)com<mailto:fabio(dot)vianello(at)salvagninigroup(dot)com>> wrote:
Is PostgreSQL a serious product? For me the answer is "NO". A product with a bug that last for years and the community knows.
It is not serious.

If you are trying to be a troll just go away, we don't need that here. If you are just venting consider that this project is no more or less likely to have oversights, incomplete documentation, or a myriad of other human induced issues than any other.

Reading the linked bug report the conclusion was "won't fix - at least not right now". Sure, it probably should have been documented but wasn't. It happens. And given the lack of complaints in the intervening years the decision, to not devote volunteer resources to a marginal feature, seems like the right one. Your active recourse at this point is to either convince a volunteer hacker to take up the cause - which your attitude doesn't help - or pay someone to do it. Or figure out a personal work-around to live with the current reality. Given that there is ongoing discussion as a result of your report (i.e., the report has merit regardless of how it was reported) means you should either meaningfully contribute to the discussion or shut up until they are done - at which point you are back to making a decision. Prompting politely for attention if the thread seems to languish without a clear resolution is, IMO, acceptable.

David J.

SALVAGNINI ITALIA S.p.A.
Via Guido Salvagnini, 51 - IT - 36040 Sarego (VI)
T. +39 0444 725111 | F. +39 0444 43 6404
Società a socio unico - Attività direz. e coord.: Salvagnini Holding S.p.A.
Clicca qui<https://www.salvagninigroup.com/company-information> per le informazioni societarie
salvagninigroup.com<https://www.salvagninigroup.com> | salvagnini.it<http://www.salvagnini.it>

Le informazioni trasmesse sono destinate esclusivamente alla persona o alla società in indirizzo e sono da intendersi confidenziali e riservate. Ogni trasmissione, inoltro, diffusione o altro uso di queste informazioni a persone o società differenti dal destinatario è proibita. Se avete ricevuto questa comunicazione per errore, per favore contattate il mittente e cancellate le informazioni da ogni computer. Questa casella di posta elettronica è riservata esclusivamente all’invio ed alla ricezione di messaggi aziendali inerenti all’attività lavorativa e non è previsto né autorizzato l’utilizzo per fini personali. Pertanto i messaggi in uscita e quelli di risposta in entrata verranno trattati quali messaggi aziendali e soggetti alla ordinaria gestione disposta con proprio disciplinare dall’azienda e, di conseguenza, eventualmente anche alla lettura da parte di persone diverse dall’intestatario della casella.

Any information herein transmitted only concerns the person or the company named in the address and is deemed to be confidential. It is strictly forbidden to transmit, post, forward or otherwise use said information to anyone other than the recipient. If you have received this message by mistake, please contact the sender and delete any relevant information from your computer. This mailbox is only meant for sending and receiving messages pertaining business matters and any other use for personal purposes is forbidden and unauthorized. Therefore, any email sent and received will be handled as ordinary business messages and subject to the company's own rules, and may thus be read also by people other than the user named in the mailbox address.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrei Zhidenkov 2020-06-10 14:30:34 pg_cancel_backend() doesn't abort a transaction
Previous Message Fan Liu 2020-06-10 01:28:57 RE: [Bus error] huge_pages default value (try) not fall back

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-06-10 06:53:53 Re: Physical replication slot advance is not persistent
Previous Message Thomas Munro 2020-06-10 05:42:16 Re: [PATCH] Add support for choosing huge page size