BRIN is 1/4570th the size of a B-tree, until 5% of rows are updated
I co-owned the Zonemaps module at Oracle, and BRIN is the same design in Postgres. It stops pruning long before pg_stats.correlation admits anything is wrong — at correlation 0.921, a 28x collapse. Measured on 10M rows, harness inline.
Summary
BRIN’s efficiency in managing data size is highlighted, showing it can significantly reduce the footprint compared to B-trees until a certain update threshold is reached. With insights from an Oracle expert, the article examines the performance implications of using BRIN with large datasets.
Comments (2 of ) ⌛