Re: Command Triggers, v16

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Thom Brown <thombrown(at)gmail(dot)com>
Subject: Re: Command Triggers, v16
Date: 2012-03-16 14:01:42
Message-ID: 7501.1331906502@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On Friday, March 16, 2012 02:50:55 PM Tom Lane wrote:
>> While I'm looking at the grammar ... it also seems like a serious
>> PITA from a maintenance standpoint that we're now going to have to
>> adjust the CREATE COMMAND TRIGGER productions every time somebody
>> thinks of a new SQL command.

> I don't find that argument really convincing.

Well, how about just plain parser size bloat? Did anyone look at
how much bigger gram.o becomes with this? Bigger parser -> slower,
for everybody, whether they care about this feature or not.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-03-16 14:08:07 Re: foreign key locks, 2nd attempt
Previous Message Andres Freund 2012-03-16 13:57:24 Re: Command Triggers, v16