| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Egor Rogov <e(dot)rogov(at)postgrespro(dot)ru> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Soumyadeep Chakraborty <soumyadeep2007(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_stats and range statistics |
| Date: | 2023-11-25 16:57:19 |
| Message-ID: | CAPpHfdsQXY5Z+9DZ1sMz5RbneBCyKGvpgP7MrNSoL41fn9Y=xw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 25, 2023 at 11:14 AM Egor Rogov <e(dot)rogov(at)postgrespro(dot)ru> wrote:
>
> Hi Alexander,
>
> On 25.11.2023 02:06, Alexander Korotkov wrote:
> >
> > In conclusion of all of the above, I decided to revise the patch and
> > show the bounds histogram as it's stored in pg_statistic. I revised
> > the docs correspondingly.
>
>
> So basically we returned to what it all has started from? I guess it's
> better than nothing, although I have to admit that two-array
> representation is much more readable. Unfortunately it brings in a
> surprising amount of complexity.
Yep, it is.
> Anyway, thanks for looking into this!
And thank you for the feedback!
------
Regards,
Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2023-11-25 17:19:45 | Improve rowcount estimate for UNNEST(column) |
| Previous Message | Alexander Korotkov | 2023-11-25 16:55:11 | Re: pg_stats and range statistics |