Re: Dynamic Partitioning using Segment Visibility Maps
От | Markus Schiltknecht |
---|---|
Тема | Re: Dynamic Partitioning using Segment Visibility Maps |
Дата | |
Msg-id | 47822215.9080200@bluegap.ch обсуждение исходный текст |
Ответ на | Re: Dynamic Partitioning using Segment Visibility Maps (Csaba Nagy <nagy@ecircle-ag.com>) |
Ответы |
Re: Dynamic Partitioning using Segment Visibility Maps
|
Список | pgsql-hackers |
Hi Csaba, Csaba Nagy wrote: > One additional thought: what about a kind of "segment fill factor" ? > Meaning: each segment has some free space reserved for future > updates/inserts of records in the same range of it's partitioning > constraint. And when inserting/updating you put the new record into the > corresponding segment... just like a very coarse clustering. Hm.. yeah. That way, a few writes to a "read optimized" segment could be accepted, without having to drop the optimization immediately. And the other way around: generally prevent having to drop the optimization by forcing tuples to be written to a segment with matching min/max tuples. Although, that's not exactly trivial, I think. However, for tables which don't fit the use case of SE, people certainly don't want such a fill factor to bloat their tables. Regards Markus
В списке pgsql-hackers по дате отправления: