hi everybody,
we've noticed a seemingly strange behaviour when
inserting fixed-size tuples into disk blocks.
We created a new table (which obviously is empty) and
we inserted some fixed-size tuples by directly using
the interface function simple_heap_insert. All the
tuple attributes are not null and fixed-size and no
primary key has been defined on the table.
The strange thing is that the number of tuples stored
on  a single block is different on each block: for
example, the first holds 272 tuples, the second 198,
the third 180 and so on. Note that the blocks are all
new as the table has been freshly created and no tuple
has ever been deleted or updated.
We repeated the process, with the same data, on
another newly created table but the blocks are filled
exactly in the same way, so it seems like this is a
behaviour based on some evaluation.
Does anybody know why this happens?

Thanks a lot!

alice and lorena

______________________________________________________________________
Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino
http://it.yahoo.com/mail_it/foot/?http://it.mobile.yahoo.com/index2002.html


Fri, 2 May 2003 17:36:39 +0200 (CEST)
=?iso-8859-1?q?Alice=20Lottini?= <alice_lottini@yahoo.it>
inserting tuples into disk blocks