Richard Huxton <dev@archonet.com> writes:
> Large table representing non-overlapping blocks:
> blocks(id int4, min varchar, max varchar)
> SELECT * FROM blocks WHERE 'ABCDE' BETWEEN min AND max;
> The estimator gets the wrong plan because it doesn't realise there's
> (at most) only one block that can match.
Even if it did realize that, it couldn't do much, because this query
isn't indexable as it stands.
I wonder whether you could adapt the "line segment" datatype
(see contrib/seg/) into a sort of "text segment" thingy and use the
GiST indexing support on that. You'd have a query likeWHERE min_max_object overlaps-operator 'ABCDE'
and the overlaps operator would be a GiST-indexable one.
regards, tom lane