| From: | Mark Rofail <markm(dot)rofail(at)gmail(dot)com> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, David Steele <david(at)pgmasters(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers-owner(at)postgresql(dot)org |
| Subject: | Re: GSoC 2017: Foreign Key Arrays |
| Date: | 2017-07-27 12:07:23 |
| Message-ID: | CAJvoCuvNuN3GrM4TSDAx3nfTkcJjNhk27HzPQEYkZHykOz6MSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 27, 2017 at 12:54 PM, Alexander Korotkov <aekorotkov(at)gmail(dot)com>
wrote:
>
> How many rows of FK table were referencing the PK table row you're
> updating/deleting.
> I wonder how may RI trigger work so fast if it has to do some job besides
> index search with no results?
>
The problem here is that the only to option for the foreign key arrays are
NO ACTION and RESTRICT which don't allow me to update/delete a refrenced
row in the PK Table. the EXPLAIN ANALYZE only tells me that this violates
the FK constraint.
So we have two options. Either implement CASCADE or if there's a
configration for EXPLAIN to show costs even if it violates the FK
constraints.
> I think we should also vary the number of referencing rows.
>
The x axis is the number if refrencing rows in the FK table
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2017-07-27 12:25:13 | Re: Transactions involving multiple postgres foreign servers |
| Previous Message | amul sul | 2017-07-27 11:41:01 | Re: [POC] hash partitioning |