Horton
Menu

Re: proposal: make NOTIFY list de-duplication optional

Vik Fearing <vik@2ndquadrant.fr>

View thread
From: Vik Fearing <vik@2ndquadrant.fr>
To: Filip Rembiałkowski <filip.rembialkowski@gmail.com>, Craig Ringer <craig@2ndquadrant.com>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2016-02-08T20:50:19Z
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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Use a hash table to de-duplicate NOTIFY events faster.