Re: Command Triggers, patch v11

From: Thom Brown <thom(at)linux(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Command Triggers, patch v11
Date: 2012-03-09 14:22:51
Message-ID: CAA-aLv5ORQ5YhcFnPphLYjpYgAVqXBbGtdMVTitGhAqw2b2PWg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9 March 2012 14:09, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Mar 7, 2012 at 4:53 PM, Thom Brown <thom(at)linux(dot)com> wrote:
>> I've also since found that if I issue a VACUUM, CLUSTER or REINDEX on
>> a read-only standby, the BEFORE ANY COMMAND trigger fires.  I don't
>> think any trigger should fire on a read-only standby.
>
> Why ever not?

Sorry, I meant any command trigger. It's because none of the commands
can be run on a standby, so the triggers don't seem appropriate.

--
Thom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-03-09 14:30:14 Re: Command Triggers, patch v11
Previous Message Robert Haas 2012-03-09 14:09:29 Re: Command Triggers, patch v11