Re: Command Triggers, v16 - Mailing list pgsql-hackers

From Thom Brown
Subject Re: Command Triggers, v16
Date
Msg-id CAA-aLv6dFDZ+hx8RH1HRQdwyq53QKmNCYJg30mnd9_TNtYJF1Q@mail.gmail.com
Whole thread Raw
In response to Re: Command Triggers, v16  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Command Triggers, v16  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On 16 March 2012 11:42, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote:
> Thom Brown <thombrown@gmail.com> writes:
>> Specific command triggers on ALTER VIEW don’t work at all:
>
> Can't reproduce, and that's already part of the regression tests.

This was a problem my side (a mistake I made previously) as I hadn't
added this particular one into my list of created command triggers.  I
had then seen the triggers fire, but forgot to go back and remove my
statement from the draft email.  Apologies.

> And I've been attaching an incremental patch too. Next patch revision is
> expected later today with support for plpython, plperl and pltcl.

Okay, I shalln't do any more testing until the next patch.  I should
probably have worked on automating my tests more, but never got round
to it.

Thom


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Command Triggers, v16
Next
From: Dimitri Fontaine
Date:
Subject: Re: Command Triggers, v16