Re: feature proposal - triggers by semantics

From: Craig Ringer <craig(at)2ndQuadrant(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
Cc: Darren Duncan <darren(at)darrenduncan(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: feature proposal - triggers by semantics
Date: 2012-11-16 01:43:27
Message-ID: 50A59A3F.1040808@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/16/2012 05:38 AM, Dimitri Fontaine wrote:
> Darren Duncan <darren(at)darrenduncan(dot)net> writes:
>> So, I'm partly proposing a specific narrow new feature, "TRUNCATE FOR EACH
>> ROW"
> Kevin has been proposing that we consider an alternative approach in
> some other cases that I think would work better for you, too. Namely, to
> have access to OLD and NEW in FOR EACH STATEMENT triggers, where they
> would be relations rather than records.

That would be an exceedingly useful feature. On the project I was
working on earlier I'd immediately rewrite quite a few of the triggers
if it became available, with results I'd expect to be both faster and
simpler.

I can see using the same facility to optimise foreign key validity
checks in the absence of an index on the foreign key column, too.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhijit Menon-Sen 2012-11-16 01:56:25 Re: [PATCH] binary heap implementation
Previous Message Simon Riggs 2012-11-16 01:26:42 Re: Do we need so many hint bits?