Re: [GENERAL] BDR replication and table triggers - Mailing list pgsql-general

From Craig Ringer
Subject Re: [GENERAL] BDR replication and table triggers
Date
Msg-id CAMsr+YGPF_gd+aOfucpiC-ag93SrnEG5Og=X_4k+LjMq_FV8ow@mail.gmail.com
Whole thread Raw
In response to [GENERAL] BDR replication and table triggers  (jamesadams89 <jamesadams80@hotmail.com>)
List pgsql-general
> 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 rows
> directly, a layer below Postgres. Is this Correct?

Yes.

>  Is there any mechanism
> that exists that could provide notifications to a listening application when
> BDR makes changes to the underlying database?

You could listen to an underlying logical decoding stream, but it
might be a bit fiddly and complex for your needs.

Ideally we'd be able to fire triggers in BDR, but that's not
implemented or on the current roadmap and there's no funded work on it
at this point. There's some work to support it in pglogical though.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] Implicit typecasting to numeric in psql
Next
From: Thomas Güttler
Date:
Subject: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in thefuture?