On 11/16/2012 05:38 AM, Dimitri Fontaine wrote: > Darren Duncan <dar...@darrenduncan.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
