From: | Jan Vicherek <honza(at)ied(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | space usage of NULL fields |
Date: | 1998-12-27 03:36:53 |
Message-ID: | Pine.LNX.4.04.9812262213380.11035-100000@ann.ied.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
a quick question (I couldn't contact postgresql.org, so I didn't check
the FAQ, but I doubt it would be there.)
When I create a table with field "nnn float8" and total row size, say
140 bytes, and then I insert a row with NULL in this field, will my record
take up those 8 bytes in physical page (say 140 bytes) or will it take up
less (like 140-8=132), i.e. will it be shortened by those 8 bytes, since
the value is NULL and no information is stored in that field ? ( I *hate*
run-on sentences :)
In general, what are the savings/overheads associated in PG with
NULL/not NULL fields ? I.e. if will I save the space if I define the field
as varchar(8) instead of float8 ?
Thanx,
Jan
-- Gospel of Jesus is the saving power of God for all who believe --
## To some, nothing is impossible. ##
http://Vicherek.Waterloo.on.ca/
From | Date | Subject | |
---|---|---|---|
Next Message | Angelos Karageorgiou | 1998-12-27 10:38:24 | Re: [HACKERS] psql \d does not work |
Previous Message | Bruce Momjian | 1998-12-26 20:10:13 | Re: [HACKERS] Re: [PATCHES] NetBSD/m68k port |