Re: [BUGS] BUG #14699: Statement trigger and logical replication

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Euler Taveira <euler(at)timbira(dot)com(dot)br>
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-07-04 03:39:35
Message-ID: 14dceb54-f510-8c4e-b3b7-412b2fd566e9@2ndquadrant.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 6/17/17 08:29, Euler Taveira wrote:
> 2017-06-16 22:08 GMT-03:00 Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com
> <mailto: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.

I have added the documentation.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Langote 2017-07-04 04:45:15 Re: BUG #14732: partitioned table cann't alter set parallel_workers?
Previous Message digoal 2017-07-04 02:09:50 BUG #14732: partitioned table cann't alter set parallel_workers?

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2017-07-04 03:49:34 Re: Get stuck when dropping a subscription during synchronizing table
Previous Message Jeff Janes 2017-07-04 03:26:20 Re: subscription worker signalling wal writer too much