| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| 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 17:13:15 |
| Message-ID: | CA+U5nMJSnKghxg_pt6e3Txn0a+3nc9j0wt0XQPoHvmiUYUSFuw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9 June 2013 14:59, Greg Stark <stark(at)mit(dot)edu> wrote:
> 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.
Exactly my thoughts.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-06-09 20:55:02 | postgres_fdw regression tests order dependency |
| Previous Message | Joshua D. Drake | 2013-06-09 16:42:15 | Re: small patch to crypt.c |