Hi Alban, Thank you for the update.
> For one thing: The table holds information regarding to which transactions > each row is visible (the xid) whereas the index does not. What would be the each value of the xid, like 8 bytes,or 32 bytes..which causing the table to hold what index is not and the space occupied is exactly half of the table in indexes. Can you explain a bit on this. Thanks in Advance Regards Raghavendra On Sun, Mar 28, 2010 at 4:52 PM, Alban Hertroys < dal...@solfertje.student.utwente.nl> wrote: > On 28 Mar 2010, at 10:05, Tadipathri Raghu wrote: > > > Hi All, > > ... > > > I like to know here is, I have created a table with one column and the > index is on one column only, so why is the space occupied differently, > almost all half of the space of the table and why not full. Could please you > explain on this. And what exactly the postgres architecture treat on Index > table and Ordinary table. > > For one thing: The table holds information regarding to which transactions > each row is visible (the xid) whereas the index does not. > > Alban Hertroys > > -- > Screwing up is an excellent way to attach something to the ceiling. > > > !DSPAM:1046,4baf3bfb10411932744907! > > >
