| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Константин Евтеев <konst583(at)gmail(dot)com> |
| Subject: | Re: [BUGS] BUG #14699: Statement trigger and logical replication |
| Date: | 2017-06-17 01:08:44 |
| Message-ID: | c020d3a1-55be-20a7-3689-cb9ad4554f8e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 6/16/17 09:13, Константин Евтеев wrote:
> 2017-06-13 5:57 GMT+03:00 Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com
> <mailto:peter(dot)eisentraut(at)2ndquadrant(dot)com>>:
>
> I think this is all working correctly and as intended.
>
> But then, why data copy for init logical replication fires statement
> trigger. May be it is also not nedeed?
> Or this feature needs to be mentioned in documentation?
I don't know. Hackers?
The issue is that the logical replication initial data copy fires a
statement trigger for INSERT, because it's implemented as a COPY internally.
By contrast, the normal apply worker does not fire any statement
triggers (because they are not "statements").
We could adjust one or the other or leave it as is.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-06-17 01:22:34 | Re: [BUGS] BUG #14699: Statement trigger and logical replication |
| Previous Message | konst583 | 2017-06-16 19:56:17 | BUG #14710: Function now() and logical replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-06-17 01:22:34 | Re: [BUGS] BUG #14699: Statement trigger and logical replication |
| Previous Message | Peter Eisentraut | 2017-06-17 01:05:22 | Re: Restrictions of logical replication |