Re: [HACKERS] GSoC 2017: Foreign Key Arrays

Поиск
Список
Период
Сортировка
От Mark Rofail
Тема Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Дата
Msg-id CAJvoCuswKzt3XYEoxigoY+j=vVBH2Ry17emEmQJHEGawejKUzw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] GSoC 2017: Foreign Key Arrays  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: [HACKERS] GSoC 2017: Foreign Key Arrays  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-hackers
Hello Alvaro,

Looking at 0001+0003, I see it claims GIN support for <<@ and @>>, but
actually only the former is implemented fully; the latter is missing a
strategy number in ginarrayproc.c and pg_amop.dat, and also
src/test/regress/sql/gin.sql does not test it.  I suspect
ginqueryarrayextract needs to be told about this too.
GIN/array_ops requires the left operand to be an array, so only @>> can be used in GIN. However, <<@ is defined as @>> commutative counterpart, so when for example “5 <<@ index” it will be translated to “index @>> index” thus indirectly using the GIN index. 

We can definitely add tests to “ src/test/regress/sql/gin.sql” to test this. Do you agree?

Also what do you mean by “ ginqueryarrayextract needs to be told about this too”?

Best Regards,
Mark Rofail

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

Предыдущее
От: "alvherre@alvh.no-ip.org"
Дата:
Сообщение: Re: libpq debug log
Следующее
От: "Joel Jacobson"
Дата:
Сообщение: Idea: Avoid JOINs by using path expressions to follow FKs