Re: Command Triggers, patch v11 - Mailing list pgsql-hackers

From Thom Brown
Subject Re: Command Triggers, patch v11
Date
Msg-id CAA-aLv60WA2rs_X7xXe0zdaKgX_n4ETDEHz0SX=n9DcMZtL39w@mail.gmail.com
Whole thread Raw
In response to Re: Command Triggers, patch v11  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On 3 March 2012 14:26, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote:
> Thom Brown <thom@linux.com> writes:
>> And having tried building it, it appears to fail.
>
> Sorry about that, my compiler here was happy building the source (and I
> had been doing make clean install along the way) and make installcheck
> passed, here.
>
> Now fixed on my github's branch, including docs.
>
> I'll send an updated patch revision later, hopefully including pg_dump
> support fixtures (well, adaptation to the new way of doing things IIUC)
> and maybe with some trigger arguments rework done.
>
> I understand that you're not blocked until that new version is out,
> right? You could use either the incremental patch attached for
> convenience.

Thanks for the extra patch.  Do you see any functional changes between
now and your next patch?  If so, it doesn't make sense for me to test
anything yet.

-- 
Thom


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Command Triggers, patch v11
Next
From: Thom Brown
Date:
Subject: Re: Command Triggers, patch v11