From: | Константин Евтеев <konst583(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14699: Statement trigger and logical replication |
Date: | 2017-06-16 13:13:36 |
Message-ID: | CAAqA9PRLsBsKj4AKyA1G22MN64ORA6s0pD4ZXYecYNmLbZu_Xw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
2017-06-13 5:57 GMT+03:00 Peter Eisentraut <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?
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-06-16 16:15:55 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
Previous Message | Heikki Linnakangas | 2017-06-16 08:49:48 | Re: BUG #14706: Dependencies not recorded properly for base types |
From | Date | Subject | |
---|---|---|---|
Next Message | Mahi Gurram | 2017-06-16 13:17:37 | Re: Regarding Postgres Dynamic Shared Memory (DSA) |
Previous Message | Etsuro Fujita | 2017-06-16 12:29:17 | Re: Bug in ExecModifyTable function and trigger issues for foreign tables |