Re: Pushing ScalarArrayOpExpr support into the btree index AM - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Pushing ScalarArrayOpExpr support into the btree index AM
Date
Msg-id 26790.1318789598@sss.pgh.pa.us
Whole thread Raw
In response to Re: Pushing ScalarArrayOpExpr support into the btree index AM  (Florian Pflug <fgp@phlo.org>)
Responses Re: Pushing ScalarArrayOpExpr support into the btree index AM
List 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 by date:

Previous
From: Florian Pflug
Date:
Subject: Re: Pushing ScalarArrayOpExpr support into the btree index AM
Next
From: Florian Pflug
Date:
Subject: Re: Underspecified window queries in regression tests