| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Optimising Foreign Key checks |
| Date: | 2013-06-09 13:59:21 |
| Message-ID: | CAM-w4HNNoUp0PR10bzmj1=pbUvAioGqwJ3QTztT6wkvt2iLjKA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jun 9, 2013 at 10:51 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> AFAICS there are weird cases where changing the way FKs execute will
> change the way complex trigger applications will execute. I don't see
> a way to avoid that other than "do nothing". Currently, we execute the
> checks following the normal order of execution rules for triggers.
> Every idea we've had so far changes that in some way; variously in
> major or minor ways, but changed nonetheless.
The obvious case to handle would be if someone has a trigger to
automatically create any missing references.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-06-09 14:44:36 | Re: Vacuum, Freeze and Analyze: the big picture |
| Previous Message | Kevin Grittner | 2013-06-09 13:56:11 | Re: Batch API for After Triggers |