From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Command Triggers, patch v11 |
Date: | 2012-03-03 15:37:02 |
Message-ID: | CAA-aLv60WA2rs_X7xXe0zdaKgX_n4ETDEHz0SX=n9DcMZtL39w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3 March 2012 14:26, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> wrote:
> Thom Brown <thom(at)linux(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2012-03-03 15:55:35 | Re: Command Triggers, patch v11 |
Previous Message | Dimitri Fontaine | 2012-03-03 14:34:59 | Re: Command Triggers, patch v11 |