Thanks Tom and Erik and all the others who helped.
You guys really rock!!!
Sharmila
You guys really rock!!!
Sharmila
----- Original Message ----
From: Tom Lane <tgl@xxxxxxxxxxxxx>
To: SHARMILA JOTHIRAJAH <sharmi_jo@xxxxxxxxx>
Cc: Erik Jones <erik@xxxxxxxxxx>; pgsql-general@xxxxxxxxxxxxxx
Sent: Wednesday, November 21, 2007 1:14:02 PM
Subject: Re: Postgres table size
SHARMILA JOTHIRAJAH <sharmi_jo@xxxxxxxxx> writes:
> 1. How do you find the MAXALIGN of the machine? And what is that used for?
pg_controldata will show "maximum data alignment". A rule of thumb is
that it's 4 on 32-bit machines and 8 on 64-bit machines, but there are
exceptions.
> 2. How does null columns account for this space.
If there are any nulls in a row then you pay for a null bitmap with 1
bit/column, but the null columns themselves aren't stored and hence
take zero space. In your example the bitmap needs 10 bits, but after
allowing for alignment the effect is that the heap tuple header gets
4 bytes bigger if there's any nulls.
regards, tom lane
From: Tom Lane <tgl@xxxxxxxxxxxxx>
To: SHARMILA JOTHIRAJAH <sharmi_jo@xxxxxxxxx>
Cc: Erik Jones <erik@xxxxxxxxxx>; pgsql-general@xxxxxxxxxxxxxx
Sent: Wednesday, November 21, 2007 1:14:02 PM
Subject: Re: Postgres table size
SHARMILA JOTHIRAJAH <sharmi_jo@xxxxxxxxx> writes:
> 1. How do you find the MAXALIGN of the machine? And what is that used for?
pg_controldata will show "maximum data alignment". A rule of thumb is
that it's 4 on 32-bit machines and 8 on 64-bit machines, but there are
exceptions.
> 2. How does null columns account for this space.
If there are any nulls in a row then you pay for a null bitmap with 1
bit/column, but the null columns themselves aren't stored and hence
take zero space. In your example the bitmap needs 10 bits, but after
allowing for alignment the effect is that the heap tuple header gets
4 bytes bigger if there's any nulls.
regards, tom lane
Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.
