Trigger overhead/performance and alternatives? - Mailing list pgsql-performance

From AJG
Subject Trigger overhead/performance and alternatives?
Date
Msg-id 1530437484973-0.post@n3.nabble.com
Whole thread Raw
Responses Re: Trigger overhead/performance and alternatives?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-performance
Hello,

Apologies if this is not in the correct forum for the non-urgent question
that follows.

I was reading the pgconf 2018 ppt slides by Jonathan Katz (from slide 110
onwards)
http://www.pgcon.org/2018/schedule/attachments/480_realtime-application.pdf

Where is mentioned trigger overhead, and provided an alternative solution
(logical replication slot monitoring).

My 2 part question is.

1) Does anybody have any benchmarks re: trigger overhead/performance or have
any experience to give a sort of indication, at all?

2) Is anybody aware of any other clever alternatives, pg extensions or
github code etc as an alternative to using triggers?

Thanks in advance,




--
Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html


pgsql-performance by date:

Previous
From: Andres Freund
Date:
Subject: Re: Bug in PostgreSQL
Next
From: José Mello Júnior
Date:
Subject: tcp_keepalives