| From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
|---|---|
| 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 12:29:37 |
| Message-ID: | CAHE3wghmzCJ8hD0DKfAJdts9iGfSazBOa+CGY=heBZVKzauN6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
2017-06-16 22:08 GMT-03:00 Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)
com>:
>
> The issue is that the logical replication initial data copy fires a
> statement trigger for INSERT, because it's implemented as a COPY
> internally.
>
> We should document such behavior. AFAICS we discuss later if we should
provide an option to fire statement triggers during initial copy.
> By contrast, the normal apply worker does not fire any statement
> triggers (because they are not "statements").
>
> +1.
> We could adjust one or the other or leave it as is.
Let's leave it as is. At least until 11.
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
<http://www.timbira.com.br>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-06-17 12:56:06 | Re: BUG #14710: Function now() and logical replication |
| Previous Message | Thomas Munro | 2017-06-17 01:51:53 | Re: [BUGS] BUG #14699: Statement trigger and logical replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2017-06-17 12:32:42 | Re: Getting server crash on Windows when using ICU collation |
| Previous Message | Erik Rijkers | 2017-06-17 10:48:52 | Re: logical replication - still unstable after all these months |