proposal: make NOTIFY list de-duplication optional

Filip Rembiałkowski <filip.rembialkowski@gmail.com>

From: Filip Rembiałkowski <filip.rembialkowski@gmail.com>
To: Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2016-02-05T15:17:40Z
Lists: pgsql-hackers

Attachments

- new GUC in "Statement Behaviour" section, notify_duplicate_removal
(default true)

Initial discussion in this thread:
http://www.postgresql.org/message-id/CAP_rwwmpzk9=SbjRZTOd05bDctyC43wNKnu_m37dYGvL4SAeSw@mail.gmail.com

Rationale: for some legitimate use cases, duplicate removal is not
required, and it gets O(N^2) cost on large COPY/ insert transactions.

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.