Re: proposal: make NOTIFY list de-duplication optional

From: Vik Fearing <vik(at)2ndquadrant(dot)fr>
To: Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: make NOTIFY list de-duplication optional
Date: 2016-02-08 20:50:19
Message-ID: 56B8FF8B.1060602@2ndquadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/08/2016 09:33 PM, Filip Rembiałkowski wrote:
> Here is my next try, after suggestions from -perf and -hackers list:
>
> * no GUC
>
> * small addition to NOTIFY grammar: NOTIFY ALL/DISTINCT
>
> * corresponding, 3-argument version of pg_notify(text,text,bool)
>
> * updated the docs to include new syntax and clarify behavior
>
> * no hashtable in AsyncExistsPendingNotify
> (I don't see much sense in that part; and it can be well done
> separately from this)

Please add this to the next commitfest:
https://commitfest.postgresql.org/9/new/
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2016-02-08 20:59:32 Re: Tracing down buildfarm "postmaster does not shut down" failures
Previous Message Alvaro Herrera 2016-02-08 20:47:05 Re: Proposal: SET ROLE hook