Re: Alter Fragment ... init ...

The admin guide uses neither term. It refers to the behavior as "Merging extents." From the 7.30 Admin Guide: Extents for the Same Table Might Merge If the disk space allocated for a next extent is physically contiguous with disk space already allocated to the same table, the database server allocates the disk space but does not consider the new allocation as a separate extent. Instead, the database server extends the size of the existing contiguous extent. Thereafter, all disk-space reports reflect the allocation as an extension of the existing extent. That is, the number of extents reported is always the number of physically distinct extents, not the number of times a next extent has been allocated plus one (the initial extent). Art S. Kagel wrote in message <3641DEF7.C87@bloomberg.net>... >Vic Goldberg wrote: >> >> Because of a concept call extent concatenation. If the database can add a >> second extent physically next to the first one, it concatenates the two, >> and just ends up with one, bigger extent. > >Correct except that Informix calls this "Extent Compression". >It's a trivial point but then I'm a trivial guy. > >Art S. Kagel