Re: Broken selectivity with special inet operators

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Broken selectivity with special inet operators
Date: 2011-09-21 21:17:48
Message-ID: 4E7A547C.40700@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 9/21/11 1:56 PM, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Guillaume Smet 2011-09-21 21:47:23 Re: BUG #6219: date_part() function producting incorrect year
Previous Message Eric Vollnogel 2011-09-21 21:17:31 BUG #6219: date_part() function producting incorrect year