Horton

Re: [PATCH] reduce page overlap of GiST indexes built using sorted method

x4mmm@yandex-team.ru

View thread View on postgr.es
From: Andrey Borodin <x4mmm@yandex-team.ru>
To: bjorn@wololo.org
Cc: Aliaksandr Kalenik <akalenik@kontur.io>, pgsql-hackers@lists.postgresql.org
Date: 2022-01-18T18:49:37Z
Lists: pgsql-hackers 

> 18 янв. 2022 г., в 03:54, Björn Harrtell <bjorn.harrtell@gmail.com> написал(а):
> 
> There might be some deep reason in the architecture that I'm unaware of that could make it difficult to affect the node size but regardless, I believe there could be a substantial win if node size could be controlled.

That's kind of orthogonal development path. Some years ago I had posted "GiST intrapage indexing" patch [0], that was aiming to make a tree with fanout that is Sqrt(Items on page). But for now decreasing fillfactor == wasting a lot of space, both in shared_buffers and on disk...

Thank you for raising this topic, I think I should rebase and refresh that patch too...

Best regards, Andrey Borodin.


[0] https://www.postgresql.org/message-id/flat/7780A07B-4D04-41E2-B228-166B41D07EEE%40yandex-team.ru

Commits

  1. Reduce non-leaf keys overlap in GiST indexes produced by a sorted build