reserving space in a rec for future update
| От | Gauthier, Dave |
|---|---|
| Тема | reserving space in a rec for future update |
| Дата | |
| Msg-id | D7FF158337303A419CF4A183F48302D603568E5C@hdsmsx411.amr.corp.intel.com обсуждение исходный текст |
| Ответы |
Re: reserving space in a rec for future update
Re: reserving space in a rec for future update |
| Список | pgsql-general |
Hi:
I have a situation where I will be inserting thousands of records into a table but leaving 2 of it’s columns null. Later on, I will be updating most of those records and putting real values in place of those 2 nulls. As for the ones that do not get updated, I want to leave them null. My concern has to do with record fragmentation at the time of update because there’s no room to “expand” them to accept the non-null data. (BTW, the columns are floating point).
Is there a way to initially insert nulls, but reserve space for the future update (and avoid record fragmentation)?
Is my record fragmentation concern unfounded?
Thanks in Advance !
В списке pgsql-general по дате отправления: