Re: MaxOffsetNumber for Table AMs
| От | Peter Geoghegan |
|---|---|
| Тема | Re: MaxOffsetNumber for Table AMs |
| Дата | |
| Msg-id | CAH2-Wz=2CvJ_z6vzY=W+HjX9QGGj8jKXQBKFpi6xMXReJutX6Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: MaxOffsetNumber for Table AMs (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: MaxOffsetNumber for Table AMs
|
| Список | pgsql-hackers |
On Wed, May 5, 2021 at 11:25 AM Andres Freund <andres@anarazel.de> wrote: > Agreed. And we can increase the fit a good bit without needing invasive > all-over changes. With those changes often even helping heap. > > E.g. tidbitmap.c's harcoded use of MaxHeapTuplesPerPage is a problem > even for heap - we waste a lot of space that's not commonly used. A > better datastructure (radix tree like I'd say, but several tree shaped > approaches seem possible). Agreed -- even if we only cared about heapam we still ought to do something about tidbitmap.c's use of MaxHeapTuplesPerPage. -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: