| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Egor Rogov <e(dot)rogov(at)postgrespro(dot)ru> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Triggers and logical replication (10devel) |
| Date: | 2017-04-21 13:29:24 |
| Message-ID: | CAHyXU0zpyLp2ySnPi4YreDbzKavcV89PC9rLwg5KNX=P1PW5Ew@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 21, 2017 at 5:08 AM, Egor Rogov <e(dot)rogov(at)postgrespro(dot)ru> wrote:
> Hello,
> It seams that tiggers don't fire on subscriber's tables during logical
> replication. Is it a bug?
Reading the documentation (which is TBH a bit hard to follow) it
appears that it is expected behavior.
"The apply process on the subscriber database always runs with
session_replication_role set to replica, which produces the usual
effects on triggers and constraints."
https://www.postgresql.org/docs/devel/static/sql-altertable.html states:
"The trigger firing mechanism is also affected by the configuration
variable session_replication_role. Simply enabled triggers will fire
when the replication role is “origin” (the default) or “local”."
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2017-04-21 13:31:42 | Re: On-disk format of SCRAM verifiers |
| Previous Message | Michael Paquier | 2017-04-21 13:21:48 | Re: On-disk format of SCRAM verifiers |