On Thu, 2019-05-02 at 01:05 -0400, Tom Lane wrote:
> Sergey Koposov writes:
> >
> > On Thu, 2019-05-02 at 00:36 -0400, Tom Lane wrote:
> > >
> > > What sort of selectivity estimator have you got attached to that custom
> > > operator?
> >
> > This is the code, but basically it is just a constan
Sergey Koposov writes:
> On Thu, 2019-05-02 at 00:36 -0400, Tom Lane wrote:
>> What sort of selectivity estimator have you got attached to that custom
>> operator?
> This is the code, but basically it is just a constant based on the search
> radius (which is the leftmost float argument of the op
On Thu, 2019-05-02 at 00:36 -0400, Tom Lane wrote:
> Sergey Koposov writes:
> >
> > I'm currently trying to understand the expected row counts for a query
> > involving a nested loop join and bitmap index scan
> > on the functional index and a custom operator. And the numbers that I see
> > do
Sergey Koposov writes:
> I'm currently trying to understand the expected row counts for a query
> involving a nested loop join and bitmap index scan
> on the functional index and a custom operator. And the numbers that I see
> don't make sense to me currently.
What sort of selectivity estimato
Hi,
I'm currently trying to understand the expected row counts for a query
involving a nested loop join and bitmap index scan
on the functional index and a custom operator. And the numbers that I see don't
make sense to me currently. Hopefully
somebody here can shed some light on it, or confi
