Re: proposal: make NOTIFY list de-duplication optional - Mailing list pgsql-hackers

From Robert Haas
Subject Re: proposal: make NOTIFY list de-duplication optional
Date
Msg-id CA+TgmoYiKedu0vUXFQHKpJ1COmT7sNJd2KOLLtXQTQc6Ztgkug@mail.gmail.com
Whole thread Raw
In response to proposal: make NOTIFY list de-duplication optional  (Filip Rembiałkowski <filip.rembialkowski@gmail.com>)
Responses Re: proposal: make NOTIFY list de-duplication optional
List pgsql-hackers
On Fri, Feb 5, 2016 at 10:17 AM, Filip Rembiałkowski
<filip.rembialkowski@gmail.com> wrote:
> - 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.

I agree with what Merlin said about this:

http://www.postgresql.org/message-id/CAHyXU0yoHe8Qc=yC10AHU1nFiA1tbHsg+35Ds-oEueUapo7t4g@mail.gmail.com

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PostgreSQL Audit Extension
Next
From: Paul Jungwirth
Date:
Subject: Re: Review: GiST support for UUIDs