Re: [HACKERS] GSoC 2017: Foreign Key Arrays
| От | Mark Rofail |
|---|---|
| Тема | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |
| Дата | |
| Msg-id | CAJvoCutsqAGau6q+L_JRrTZozmwts8DYrO_oGJaJmrWjBd3rgA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] GSoC 2017: Foreign Key Arrays ("Joel Jacobson" <joel@compiler.org>) |
| Ответы |
Re: [HACKERS] GSoC 2017: Foreign Key Arrays
|
| Список | pgsql-hackers |
Hey Joel,
test opr_sanity ... FAILEDAND binary_coercible(p2.opcintype, p1.amoplefttype));amopfamily | amopstrategy | amopopr------------+--------------+----------(0 rows)+ 2745 | 5 | 6105+(1 row)-- Operators that are primary members of opclasses must be immutable (else-- it suggests that the index ordering isn't fixed). Operators that are
This is due using anycompatiblearray for the left operand in @>>.
To solve this problem we need to use @>>(anyarray,anyelement) or introduce a new opclass for gin indices.
These are the two approaches that come to mind to solve this. Which one is the right way or is there another solution I am not aware of?
That’s why I’m asking this on the mailing list, to get the community’s input.
/Mark
В списке pgsql-hackers по дате отправления: