Horton
Menu

Re: pg_stats and range statistics

Egor Rogov <e.rogov@postgrespro.ru>

View thread
From: Egor Rogov <e.rogov@postgrespro.ru>
To: Alexander Korotkov <aekorotkov@gmail.com>, jian he <jian.universality@gmail.com>
Cc: "Gregory Stark (as CFM)" <stark.cfm@gmail.com>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Justin Pryzby <pryzby@telsasoft.com>, Soumyadeep Chakraborty <soumyadeep2007@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2023-11-25T09:14:24Z
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!

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Collect and use histograms of lower and upper bounds for range types.