| From: | Doug Safreno <doug(at)avinetworks(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Gregory Cox <gcox(at)avinetworks(dot)com>, Sambit Das <sambit(dot)das(at)avinetworks(dot)com>, Vivek Kalyanaraman <vivek(at)avinetworks(dot)com>, Anand Parthasarathy <anpartha(at)avinetworks(dot)com>, webapp-dev <webapp-dev(at)avinetworks(dot)com> |
| Subject: | Re: Bug: Deferred FKey Check Happening on Double Update, Not Single |
| Date: | 2019-02-16 00:11:04 |
| Message-ID: | CAA=+orsauoKK_qit6kpe9TUYhUATkLQWFUPp2VOhEdN23p3+3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Gotcha, thanks for explanation.
Best,
Doug
On Fri, Feb 15, 2019 at 3:15 PM Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
wrote:
> >>>>> "Doug" == Doug Safreno <doug(at)avinetworks(dot)com> writes:
>
> Doug> Hey Sergei,
>
> Doug> Neither transaction touches FK fields - so shouldn't they both
> Doug> skip FK trigger check?
>
> The optimization that lets the check be skipped only applies on the
> _first_ modification of the row within the transaction. On the second or
> subsequent modifications, the code can't easily tell whether the row was
> inserted in the current transaction (in which case the optimization must
> be skipped) or just modified, so it assumes the worst.
>
> --
> Andrew (irc:RhodiumToad)
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-02-16 00:13:08 | Re: BUG #15631: Generated as identity field in a temporary table with on commit drop corrupts system catalogs |
| Previous Message | Andrew Gierth | 2019-02-15 23:15:25 | Re: Bug: Deferred FKey Check Happening on Double Update, Not Single |