On 6/16/17 09:13, Константин Евтеев wrote: > 2017-06-13 5:57 GMT+03:00 Peter Eisentraut > <peter.eisentr...@2ndquadrant.com > <mailto:peter.eisentr...@2ndquadrant.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 -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers