From: | "Zubkovsky, Sergey" <Sergey(dot)Zubkovsky(at)transas(dot)com> |
---|---|
To: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Row size overhead |
Date: | 2008-03-20 14:24:38 |
Message-ID: | 528853D3C5ED2C4AA8990B504BA7FB850106DF21@sol.transas.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for your reply.
I had used PG 8.3.1 on 32-bit WinXP platform.
"PostgreSQL 8.3.1, compiled by Visual C++ build 1400"
But I suppose this fact doesn't change anything essentially.
Thanks,
Sergey Zubkovsky
-----Original Message-----
From: Pavan Deolasee [mailto:pavan(dot)deolasee(at)gmail(dot)com]
Sent: Wednesday, March 19, 2008 8:23 PM
To: Zubkovsky, Sergey
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Row size overhead
2008/3/19 Zubkovsky, Sergey <Sergey(dot)Zubkovsky(at)transas(dot)com>:
>
> Simple calculations show that each row occupies 76 bytes
approximately.
>
> But anticipated row size would be 41 or near.
>
You haven't mentioned PG version. For 8.2 onwards, the tuple header is
23 bytes. Add another 4 bytes for one line pointer for each row. If you
have
null values, another 5 bytes for null bitmap and alignment. Plus add few
bytes
for page header and any unusable space in a page (because a row can not
fit in the remaining space).
Also ISTM that you might be loosing some space because of alignment
in the tuple itself. Try moving booleans and char(3) at the end. There
is not
much you can do with other overheads.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-20 14:40:13 | Re: [HACKERS] tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3 |
Previous Message | Angus B. Atkins-Trimnell | 2008-03-20 14:12:23 | Re: Function Returning SETOF RECORD: Trouble With Char Type |