| От | Integration |
|---|---|
| Тема | My 2c on adjustable blocksizes |
| Дата | |
| Msg-id | 199801060408.XAA32273@lessing.oit.umass.edu обсуждение исходный текст |
| Список | pgsql-hackers |
I would like to stand up as being very much in favor of two related things: (1) adjustable blocksizes (2) a larger MAX TUPLE size As far as I can tell (and that ain't far), there would only be relatively minor changes that would have to be made to give the option of allowing the user to select 2, 4, 8 or 16 as the blocksize. Concurrently, it would seem wise to simply up the max tuple size to 32k. It seems to me unlikely that this would have a noticeable performance impact. In order to do this, we would need to know about the 32 bit ItemIdData structure in /storage/itemid.h (see my previous posts). It was recommended to me that lp_flags might still be only using 2 of the 6 bits allocated to it. If so, increasing lp_offset to 15 and lp_len to 15, i.e. 2^15 bits, i.e. 32768 bytes max tuple size, would be possible! I think! Just my 2 cents. Eddie
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера