From: | Francisco Reyes <lists(at)natserv(dot)com> |
---|---|
To: | pgsql General List <pgsql-general(at)postgresql(dot)org> |
Subject: | |
Date: | 2002-07-04 18:06:31 |
Message-ID: | 20020704120156.Q4321-100000@zoraida.natserv.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On the FAQ we have:
CHAR() is best when storing strings that are usually the
same length. VARCHAR() is best when storing variable-length strings,
but you want to limit how long a string can be. TEXT is for strings
of unlimited length, maximum 1 gigabyte. BYTEA is for storing
binary data, particularly values that include NULL bytes.
How much space does "NULL" takes on a varchar.
I have a table where possibly less than 40% of the records will have a
value. I am wondering if I should go with a second table for those that
have the values or if NULL is small enough that it won't be much an
overhead for the possibly 60% instances when the column would be empty.
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Harding | 2002-07-04 18:13:44 | Re: repeatable crash generating two column index |
Previous Message | Herbert Liechti | 2002-07-04 18:05:03 | Re: query problem in 7.2.1: serious planner issue |