ST_Intersects not using indices

[strk]

That's due to STRICTness of the function, see #1410

[strk]

Can't confirm myself ST_Intersect(vector,vector) being non-strict. To check:

select proname, proargnames, proisstrict from pg_proc where proname = 'st_intersects';

[strk]

But among the _st_intersects the vector one is now the _only_ strict function. Robe, can you check if it hurts ?

[robe]

strk — didn't check before upgrading my db, but my ST_Intersects for vector works fine , and my raster one works fine too (I mean it uses the index) , and proisstrict is false for all 8 variants of st_intersects we have which is the way it should be.

What is this you are seeing?

[strk]

Uhm, by including also the _ prefixed variants I do see a strict one:

 _st_intersects | {geom1,geom2}               | t

Actually, I guess the _ prefixed variants could be STRICT just fine, couldn't them ? Anyway, there's nothing I'm personally seeing as I was just reporting something seen by someone else. Will close this and let the original reporter take care of it.

[robe]

correct the _st s should be strict. It's just where you need the sql to be able to break into its parts that can't be strict.

[strk]

It may be worth another ticket for _st_intersect versions being non-strict (the raster ones)

[Bborie Park]

_st_intersects(raster, raster) now STRICT as of r8714.