On Sat, 2005-08-20 at 21:25, Matt L. wrote:
> Out of curiousity,
>
> 1. Does a boolean column occupy 1byte of disk whether
> or not the value is null or not?
No. Nulls are stored, one bit per, to a byte at a time. I.e. if you
have 8 null fields, they are stored in the same byte.
> 2. Is matc
Matt L. wrote:
Out of curiousity,
1. Does a boolean column occupy 1byte of disk whether
or not the value is null or not?
I believe so.
2. Is matching on IS NULL or = 0 more efficient?
Hmm... = 0 is the same as IS FALSE. Not the same as IS NULL. So I
guess it is apples v. oranges.
Out of curiousity,
1. Does a boolean column occupy 1byte of disk whether
or not the value is null or not?
2. Is matching on IS NULL or = 0 more efficient?
3. If I ix'd columns w/ null does postgres know
whatevers not indexed is null or would their be no
point?
I currently utilize null fields
