From: | "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | reserving space in a rec for future update |
Date: | 2007-11-14 15:28:30 |
Message-ID: | D7FF158337303A419CF4A183F48302D603568E5C@hdsmsx411.amr.corp.intel.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 !
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2007-11-14 15:36:44 | Re: Using generate_series to create a unique ID in a query? |
Previous Message | Tom Lane | 2007-11-14 15:26:52 | Re: Using generate_series to create a unique ID in a query? |