Re: A thought on Index Organized Tables

<br /><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204);
margin:0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> 1) transaction information in index<br /><br />    This seems like a lot
ofbloat in indexes. It also means breaking<br /> a lot of other optimizations such as being able to read the tuples<br
/>directly from the heap page without locking. I'm not sure how much<br /> those are worth though. But adding 24 bytes
toevery index entry seems<br /> pretty unlikely to be a win anyways.<br /><br /></blockquote></div><br />Greg,<br
/>         I think, somewhere things have been misunderstood. we only need 8 bytes more per index entry. I thought
Postgreshas a 8 byte transaction id, but it is only 4 bytes, so we only need to save the insertion and deletion xids.
So8 bytes more per tuple.<br /><br />Gokul.<br />