3 ms·
That made sense. I was following along, and then all of a sudden, it just kind of ended. As a layman who doesn't clearly remember B Trees, it would be awesome
by AlexeyMK 6y ago
That made sense. I was following along, and then all of a sudden, it just kind of ended.
As a layman who doesn't clearly remember B Trees, it would be awesome to have even a sentence at the end, like
...and that's B Trees! Commonly used for storing fields in relational databases, filesystems, and more!
For fellow laymen, https://en.wikipedia.org/wiki/B-tree https://en.wikipedia.org/wiki/B-tree isn't bad, but is there more?
- why-el 6y agoThe Postgres documentation on btrees is absolutely stellar if you can afford some extended time to study it [1]. From there you can read the actual code or watch some videos on how Postgresql indexes use them. You can even dump indexes locally to see their content! from root all the way to the leaf nodes [2] (this assuming you read and understood the above). [1] https://github.com/postgres/postgres/tree/master/src/backend/access/nbtree https://github.com/postgres/postgres/tree/master/src/backend... [2] https://www.postgresql.org/docs/10/pageinspect.html https://www.postgresql.org/docs/10/pageinspect.html
- auraham 6y agoTotally agree. The first example was clear and intuitive, but I was lost when the author outlined the idea of blocks indexing blocks indexing values. Maybe an additional example could clearify this subject, improving considerably the quality of the post.