| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Константин Евтеев <konst583(at)gmail(dot)com> |
| Subject: | Re: [BUGS] BUG #14699: Statement trigger and logical replication |
| Date: | 2017-06-17 01:22:34 |
| Message-ID: | 20170617012234.k373n2zh4vlnweit@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 2017-06-16 21:08:44 -0400, Peter Eisentraut wrote:
> 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.
Leave it as is.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-06-17 01:51:53 | Re: [BUGS] BUG #14699: Statement trigger and logical replication |
| Previous Message | Peter Eisentraut | 2017-06-17 01:08:44 | Re: [BUGS] BUG #14699: Statement trigger and logical replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-06-17 01:27:01 | Re: Getting server crash on Windows when using ICU collation |
| Previous Message | Peter Eisentraut | 2017-06-17 01:08:44 | Re: [BUGS] BUG #14699: Statement trigger and logical replication |