Skip site navigation (1) Skip section navigation (2)

Re: Statistics and selectivity estimation for ranges

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Subject: Re: Statistics and selectivity estimation for ranges
Date: 2013-01-04 08:42:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, Dec 10, 2012 at 11:21 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> And I have a few other questions/comments:
> * Why is "summ" spelled with two "m"s? Is it short for "summation"? If
> so, might be good to use "summation of" instead of "integrate" in the
> comment.


> * Why does get_length_hist_frac return 0.0 when i is the last value? Is
> that a mistake?

Comment was wrong. Actually it return fraction fraction of ranges which
length is *greater*.

> * I am still confused by the distinction between rbound_bsearch and
> rbound_bsearch_bin. What is the intuitive purpose of each?

I've added corresponding comments. rbound_bsearch is for scalar operators
and for bin corresponding to upper bound. rbound_bsearch_bin is
now rbound_bsearch_bin_lower. It is for bin corresponding to lower bound.

* You use "constant value" in the comments in several places. Would
> "query value" or "search key" be better?

Yes. Fixed.

I also renamed get_length_hist_frac to get_length_hist_summ and rewrote
comments about it. Hope it becomes more understandable.

With best regards,
Alexander Korotkov.

Attachment: range_stat-0.10.patch.gz
Description: application/x-gzip (8.9 KB)

In response to


pgsql-hackers by date

Next:From: Pavel StehuleDate: 2013-01-04 09:48:03
Subject: lock AccessShareLock on object 0/1260/0 is already held
Previous:From: Josh KupershmidtDate: 2013-01-04 02:36:37
Subject: bad examples in pg_dump README

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group