Re: [HACKERS] GSoC 2017: Foreign Key Arrays
| От | Alexander Korotkov |
|---|---|
| Тема | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |
| Дата | |
| Msg-id | CAPpHfdsd9cvKzcdHgFaPLtF0MiopyGHCfUb4wVkVrPgg4vNkZA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] GSoC 2017: Foreign Key Arrays (Mark Rofail <markm.rofail@gmail.com>) |
| Ответы |
Re: [HACKERS] GSoC 2017: Foreign Key Arrays
|
| Список | pgsql-hackers |
On Tue, Aug 8, 2017 at 4:12 PM, Mark Rofail <markm.rofail@gmail.com> wrote:
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
On Tue, Aug 8, 2017 at 2:25 PM, Alexander Korotkov <aekorotkov@gmail.com> wrote:Do we already assume that default btree opclass for array element type matches PK opclass when using @>> operator on UPDATE/DELETE of referenced table?I believe so, since it's a polymorphic function.
If so, we don't introduce additional restriction here...You mean to remove the wrapper query ?
I think we should choose the query which would be better planned (and presumably faster executed). You can make some experiments and then choose the query.
GROUP BY would also use default btree/hash opclass for element type. It doesn't differ from DISTINCT from that point.Then there's no going around this limitation,
That seems like this.
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
В списке pgsql-hackers по дате отправления: