Re: Command Triggers, patch v11

From: Thom Brown <thom(at)linux(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Command Triggers, patch v11
Date: 2012-03-15 12:03:03
Message-ID: CAA-aLv5DxzW2FuBoYtbFA-g1zpnHhOqY=RnqsteLYB6+sXpmFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14 March 2012 21:33, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> wrote:
> Ok, I've implemented that. No patch attached because I need to merge
> with master again and I'm out to sleep now, it sometimes ring when being
> on-call…
>
> Curious people might have a look at my github repository where the
> command_triggers branch is updated:

Will you also be committing the trigger function variable changes
shortly? I don't wish to test anything prior to this as that will
involve a complete re-test from my side anyway.

--
Thom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message stuart 2012-03-15 13:13:29 BUG #6532: pg_upgrade fails on Python stored procedures
Previous Message Etsuro Fujita 2012-03-15 09:50:44 Re: CREATE FOREGIN TABLE LACUNA