From: | Egor Rogov <e(dot)rogov(at)postgrespro(dot)ru> |
---|---|
To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | "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 09:14:24 |
Message-ID: | c5cf801d-5ef6-5c5e-40bd-3950443c6c24@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
Anyway, thanks for looking into this!
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-11-25 11:05:23 | Re: undetected deadlock in ALTER SUBSCRIPTION ... REFRESH PUBLICATION |
Previous Message | jian he | 2023-11-25 08:57:49 | Re: pg_stats and range statistics |