proposal: make NOTIFY list de-duplication optional

From: Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>
To: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: proposal: make NOTIFY list de-duplication optional
Date: 2016-02-05 15:17:40
Message-ID: CAP_rwwn2z0gPOn8GuQ3qDVS5+HgEcG2EzEOyiJtcA=vpDEhoCg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

- 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.

Attachment Content-Type Size
postgres-async-notify-duplicate-removal-guc.patch text/x-patch 5.1 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2016-02-05 16:08:52 Re: Sanity checking for ./configure options?
Previous Message Ashutosh Bapat 2016-02-05 14:09:55 Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)