Re: [HACKERS] GSoC 2017: Foreign Key Arrays

Поиск
Список
Период
Сортировка
От Mark Rofail
Тема Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Дата
Msg-id CAJvoCutDxVvxD+3nx=m3z3++arzEfcrjV59YLkgBVfMMHU=hWQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] GSoC 2017: Foreign Key Arrays  (Alexander Korotkov <aekorotkov@gmail.com>)
Список pgsql-hackers
Okay, so I'm trying to test the performance of Foreign Key Array for 3 scenarios: Original Patch, After My Modifications and After My Modifications with GIN index on the referencing column.

I have attached the sql test file here. It contains about 10k row insertions.

However, there is a bug that prevented me from testing the third scenario, I assume there's an issue of incompatible types problem since the right operand type is anyelement and the supporting procedures expect anyarray.
I am working on debugging it right now.

But if it comes to it, should I introduce a new opclass specifically for 
anyelement or add new supporting procedures to the old opclass ? .

I have also attached the results for the first 2 scenarios, however, the third scenario is the most important one since it's what the project is all about.




Also, this is kind of interesting. Upon reviewing the results

SELECT 1 FROM ONLY fktable x WHERE $1 @> fkcol FOR SHARE OF x;

produces worse results than the original

SELECT 1 FROM ONLY fktable x WHERE $1 = ANY (fkcol) FOR SHARE OF x;

so personally I don't think we should leave creating a GIN index up to the user, it should be automatically generated instead.
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] Buildfarm failure and dubious coding in predicate.c
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: [HACKERS] Syncing sql extension versions with shared library versions