Re: per-statement-level INSTEAD OF triggers - Mailing list pgsql-hackers

From Emre Hasegeli
Subject Re: per-statement-level INSTEAD OF triggers
Date
Msg-id CAE2gYzwW9rq0Qe9QvKCqeL0qkqMJ61=Y0TgV39Wm5U1h5tCEtQ@mail.gmail.com
Whole thread Raw
In response to Re: per-statement-level INSTEAD OF triggers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> It might be more useful after we get the infrastructure that Kevin's been
> working on to allow collecting all the updates into a tuplestore that
> could be passed to a statement-level trigger.  Right now I tend to agree
> that there's little point.

Maybe, this can be used to re-implement FOREIGN KEYs.  Never-ending
bulk DELETEs caused by lack of indexes on foreign key columns are
biting novice users quite often in my experience.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Set log_line_prefix and application name in test drivers
Next
From: Peter Geoghegan
Date:
Subject: Re: Parallel tuplesort, partitioning, merging, and the future