Re: Broken selectivity with special inet operators

On 9/21/11 1:56 PM, Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
>> Summary: special inet operators ( << >> <<= =>> ) are
>>     up to 1000000X off in estimating rowcounts
>
> A look in pg_operator will show you that these operators have no
> associated selectivity estimators at all.  It's not so much "broken"
> as "unimplemented".

Oh!  I was assuming that the special case code kicked in regardless.

So we implemented the rewrite to < and > for the actual execution, but
not for cost estimates?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com