Re: BUG #14310: Triggers do not fire

From: Willy-Bas Loos <willybas(at)gmail(dot)com>
To: Iurii Popov <iurii(dot)i(dot)popov(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14310: Triggers do not fire
Date: 2017-01-03 11:07:40
Message-ID: CAHnozTiuzyMGCJ4b8w=S5z9rmZzsS6-8z-5Z=w6L+fAu4D0oZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Sep 26, 2016 at 4:29 PM, Iurii Popov <iurii(dot)i(dot)popov(at)gmail(dot)com>
wrote:

> We also use Londiste 3 from Skytools. It seems londiste disables triggers
> via set session_replication_role = 'replica' and associated with the
> connection transactions do not fire triggers.
>
> --
> Iurii Popov
>

Hi, this comes a bit late, but it might be handy for future reference.
You can set tgenabled='A' for the trigger with an update query and it will
make the trigger fire, regardless of the session_replication_role.
Specifics can be found in the docs: http://www.postgresql.org/
docs/9.4/static/catalog-pg-trigger.html

Cheers,

--
Willy-Bas Loos

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message marc 2017-01-04 08:56:05 BUG #14484: ERROR: missing chunk number 0 for toast value
Previous Message Pavel Stehule 2017-01-03 07:46:15 Re: BUG #14483: Prepared statement does not re-plan while it should