Re: Overloaded && operator from intarray module prevents index usage.
От | Michael Lewis |
---|---|
Тема | Re: Overloaded && operator from intarray module prevents index usage. |
Дата | |
Msg-id | CAHOFxGpW7JkX8HGW4MFFrSagCdW08yM-DK1jZvRJnj7dp84m=A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Overloaded && operator from intarray module prevents index usage. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Overloaded && operator from intarray module prevents index usage.
Re: Overloaded && operator from intarray module prevents index usage. |
Список | pgsql-general |
Yeah, because it's an exact datatype match while the core operator
is anyarray && anyarray which is not.
Can you dumb down how to change the index or column type such that an index will be used for the && operator while intarray extension is installed? We have the intarray extension installed and I doubt that I can get it removed. I've added gin index on a column declared as type "integer array" and had expected the index to be used, but I did not test it yet since there is some bad data with NULLs stored as a value in the integer array and I am waiting on that data cleanup to be done before directly using && operator. I expect that when I do test it, I will be impacted by this same concern. It is simplest to change the column type from integer array to anyarray? Is there a con to doing so?
В списке pgsql-general по дате отправления: