From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Export user visible function to make use of convert_to_scalar |
Date: | 2007-07-31 19:09:56 |
Message-ID: | 87bqds1jaz.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>> When complaining I hadn't read the pghackers thread in which you
>>> suggested this, and now that I'm caught up on email I remain
>>> unconvinced. What do you need convert_to_scalar for in order to display
>>> the pg_statistic histogram? You've already got the underlying data.
>
>> Then the charting tool would have to duplicate all the same code that
>> convert_to_scalar has to figure out what to do with the data.
>
> How so? The entries in the histogram are equidistant by definition.
Huh? They have equal number of values between them, they're not equidistant in
the scalar space. So the area of each bar should be the same but the width
would be proportional to the width of the bucket and the height inversely
proportional.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-07-31 20:19:10 | Re: Export user visible function to make use of convert_to_scalar |
Previous Message | Stephen Frost | 2007-07-31 18:52:39 | Re: [PATCHES] allow CSV quote in NULL |