Hello,
I've noticed that all custom operators or inet type (such as <<, <<=, etc)
cannot use an index, even though it is possible to define such an
operation on an index, for ex:
X << Y can be translated to "X >= network(Y) && X <= broadcast(Y)" (or so)
According to docs, postgres has hard-coded the ops which match index types
(such as btree for <,>,=, etc and rtree for @, etc). Is there a better way
than hardcoding support for inet types into index-selection code?
-alex