Re: Pushing ScalarArrayOpExpr support into the btree index AM
| От | Tom Lane |
|---|---|
| Тема | Re: Pushing ScalarArrayOpExpr support into the btree index AM |
| Дата | |
| Msg-id | 26790.1318789598@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Pushing ScalarArrayOpExpr support into the btree index AM (Florian Pflug <fgp@phlo.org>) |
| Ответы |
Re: Pushing ScalarArrayOpExpr support into the btree index AM
|
| Список | pgsql-hackers |
Florian Pflug <fgp@phlo.org> writes:
> On Oct16, 2011, at 19:09 , Tom Lane wrote:
>> That doesn't seem like the same thing at all, because the indexed column
>> is on different sides of the expression in the two cases. The situation
>> that I'm worried about is "indexedcolumn op ANY(arrayconstant)", and
>> what you're bringing up is "constant op ANY(indexedarraycolumn)".
> Couldn't we teach the main executor to push a ScalarArrayOpExpr down
> into the index AM if the operator belongs to the index's opclass, one
> side is indexed, and the other is constant?
Well, no, unless you're proposing to somehow implement the "constant op
ANY(indexedarraycolumn)" case in all the AMs. I don't see any practical
way to do it in btree, for one.
regards, tom lane
В списке pgsql-hackers по дате отправления: