RE: NOTIFY and pg_notify performance when deduplicating notifications - Mailing list pgsql-hackers

From
Subject RE: NOTIFY and pg_notify performance when deduplicating notifications
Date
Msg-id 028301d45fca$020595e0$0610c1a0$@jdemoor.com
Whole thread Raw
In response to Re: NOTIFY and pg_notify performance when deduplicating notifications  (Catalin Iacob <iacobcatalin@gmail.com>)
Responses Re: NOTIFY and pg_notify performance when deduplicating notifications  (Catalin Iacob <iacobcatalin@gmail.com>)
List pgsql-hackers
> Indeed, I have the same and am very interested in this.
>
> > I hope this patch can be reviewed and included in PostgreSQL.
>
> I added this to the next Commitfest and added myself as a reviewer.
> Will try to a review beginning of next week.
> https://commitfest.postgresql.org/20/1820/

Thank you for reviewing.

I just caught an error in my patch, it's fixed in the attachment. The 'never' and 'maybe' collapse modes were mixed up
inone location. 

I can't find a reasonable way to build a regression test that checks whether notifications are effectively
deduplicated.The output of the LISTEN command lists the PID of the notifying backend for each notification, e.g. :
'Asynchronousnotification "foobar" received from server process with PID 24917'. I can't just add this to async.out. I
didtest manually for all eight combinations : four collapse mode values (missing, empty string, 'maybe' and 'never'),
bothwith NOTIFY and pg_notify(). 

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: partition tree inspection functions
Next
From: Alvaro Herrera
Date:
Subject: Re: Refactor textToQualifiedNameList()