From: AJG <ayden@gera.co.nz>
To: pgsql-performance@postgresql.org
Subject: Trigger overhead/performance and alternatives?
Date: Sun, 1 Jul 2018 02:31:24 -0700 (MST)
Message-ID: <1530437484973-0.post@n3.nabble.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ayden@gera.co.nz
Subject: Re: Trigger overhead/performance and alternatives?
In-Reply-To: <1530437484973-0.post@n3.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox