Trigger overhead/performance and alternatives?

From: AJG <ayden(at)gera(dot)co(dot)nz>
To: pgsql-performance(at)postgresql(dot)org
Subject: Trigger overhead/performance and alternatives?
Date: 2018-07-01 09:31:24
Message-ID: 1530437484973-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message José Mello Júnior 2018-07-04 13:19:41 tcp_keepalives
Previous Message Andres Freund 2018-06-28 16:13:16 Re: Bug in PostgreSQL