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
