| From: | Emre Hasegeli <emre(at)hasegeli(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: per-statement-level INSTEAD OF triggers |
| Date: | 2016-08-10 21:29:54 |
| Message-ID: | CAE2gYzwW9rq0Qe9QvKCqeL0qkqMJ61=Y0TgV39Wm5U1h5tCEtQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-08-10 21:49:51 | Re: Parallel tuplesort, partitioning, merging, and the future |
| Previous Message | Tom Lane | 2016-08-10 21:18:22 | Re: Set log_line_prefix and application name in test drivers |