From: | Tadipathri Raghu <traghu(dot)dba(at)gmail(dot)com> |
---|---|
To: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Why index occupy less amount of space than the table with same structure. |
Date: | 2010-03-29 04:03:26 |
Message-ID: | 645d9d71003282103i3f3b3c30gb7c04a0985641b13@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 <
dalroi(at)solfertje(dot)student(dot)utwente(dot)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!
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ehsan Haq | 2010-03-29 04:04:58 | Re: Moving data directory from one server to another |
Previous Message | Andy Colson | 2010-03-29 01:59:24 | Re: simultaneously reducing both memory usage and runtime for a query |