Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> No surprise, see AsyncExistsPendingNotify. You would have a lot of other
> performance issues with sending hundreds of thousands of distinct notify
> events from one transaction anyway, so I can't get terribly excited about
> this.
@Filip: you probably want a per-statement trigger rather than a per-row
trigger: insert all rows with COPY, then send one notification.
You have to mark the new rows somehow yourself; unfortunately PostgreSQL
has no way to tell them in a statement trigger.