Re: BUG #14699: Statement trigger and logical replication

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: konst583(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14699: Statement trigger and logical replication
Date: 2017-06-13 02:57:31
Message-ID: cf941ded-1f8e-08b0-d864-e83c1768f27b@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 6/9/17 12:01, konst583(at)gmail(dot)com wrote:
> I have found a bug in logical replication and statement trigger on
> subscriber.
> Statement trigger works on initialisation table statement.
> But then it doesn't work.

The inserting of rows from the stream is not a "statement". Therefore,
statement triggers are not fired for that.

The initial data copy is implemented as a COPY command, which is why
statement triggers fire for that.

I think this is all working correctly and as intended.

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message naveen7eceindia 2017-06-13 05:24:49 BUG #14704: How to create unique index with a case statement?
Previous Message Peter Eisentraut 2017-06-13 02:36:00 Re: BUG #14703: documentation bug:

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-06-13 03:04:29 Why are we restricting exported snapshots in subtransactions?
Previous Message Michael Paquier 2017-06-13 02:16:54 Re: Race conditions with WAL sender PID lookups