From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Command Triggers, v16 |
Date: | 2012-03-16 11:57:23 |
Message-ID: | CAA-aLv6dFDZ+hx8RH1HRQdwyq53QKmNCYJg30mnd9_TNtYJF1Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 16 March 2012 11:42, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> wrote:
> Thom Brown <thombrown(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2012-03-16 12:07:45 | Re: Command Triggers, v16 |
Previous Message | Dimitri Fontaine | 2012-03-16 11:42:20 | Re: Command Triggers, v16 |