| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | bjorn(at)wololo(dot)org |
| Cc: | Aliaksandr Kalenik <akalenik(at)kontur(dot)io>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] reduce page overlap of GiST indexes built using sorted method |
| Date: | 2022-01-18 18:49:37 |
| Message-ID: | 6D17898F-7E2D-46DA-BDBF-0A4B5C868B3F@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 18 янв. 2022 г., в 03:54, Björn Harrtell <bjorn(dot)harrtell(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-01-18 18:50:57 | pgsql: Modify pg_basebackup to use a new COPY subprotocol for base back |
| Previous Message | Peter Geoghegan | 2022-01-18 18:48:24 | Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations |