From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
Cc: | Joe Abbate <jma(at)freedomcircle(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: CREATE EVENT TRIGGER syntax |
Date: | 2013-08-05 16:42:26 |
Message-ID: | 20130805164226.GB11189@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 19, 2013 at 05:12:16PM -0700, Dimitri Fontaine wrote:
> Joe Abbate <jma(at)freedomcircle(dot)com> writes:
> > What is the purpose of the [ AND ... ] at the end of the WHEN clause?
> > Is that for later releases, when presumably additional filter_variables
> > will be introduced? Right now, if I add "AND tag IN ..." I get an
>
> Yes. I had other filter variables in some versions of the patch, but
> we're yet to agree on a design for the things I wanted to solve with
> them.
>
> See http://www.postgresql.org/message-id/m2txrsdzxa.fsf@2ndQuadrant.fr
> for some worked out example of the CONTEXT part of the Event Trigger
> proposal.
So do we want to keep that "AND" in the 9.3beta and 9.4 documentation?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-08-05 16:46:11 | Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
Previous Message | Josh Berkus | 2013-08-05 16:41:52 | Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |