Обсуждение: Trigger overhead/performance and alternatives?
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
On 01.07.18 11:31, AJG wrote: > 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? That really depends on a lot of things, how you write the triggers, what they do, etc. You should probably measure that yourself. > 2) Is anybody aware of any other clever alternatives, pg extensions or > github code etc as an alternative to using triggers? Maybe wal2json will give you a starting point. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services