Re: Command Triggers

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Greg Smith <greg(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: Command Triggers
Date: 2012-02-15 22:21:42
Message-ID: CA+TgmoZyrZLFvhFeD8YtG3k+A18x-CyTVNz=4q416PByNCnwHA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 15, 2012 at 4:32 PM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)fr> wrote:
> Ok, I can perfectly understand that.  The principled implementation is
> not saving us here, we still need to review each call site.  The way I
> read your comment, I continue working on my big patch and we'll see what
> pieces get in, right?

Yeah, I think that makes sense. I'll have a look at your next version
when it shows up.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-02-15 22:26:16 Re: run GUC check hooks on RESET
Previous Message Josh Berkus 2012-02-15 22:18:03 Google Summer of Code? Call for mentors.