> However if I perform any INSERT, UPDATE or DELETE operations on
> DB2 and these changes propagate over to DB1 via BDR I do not see DB1 firing
> any triggers. Is this intended behavior?
Yes.
> My current understanding is that
> BDR is unable to invoke Postgres triggers as it operates on the row
Why not using the logical decoding feature:
https://www.postgresql.org/docs/9.4/static/logicaldecoding-example.html
On both sides, you would have a process that regularly decodes the stream
and emits notifications for event in tables you are insterested in.
Sylvain
2017-05-02 18:18 GMT+02:00 Alv
Hi.
It's not like BDR is unable to replicate triggers across the cluster: BDR is
not intended to do so.
BDR replicates everything that happens inside a transaction; that includes both
SQL run directly from the application, as well as changes made by triggers and
extensions. As the changes are
