Re: Proposal for Null Bitmap Optimization(for Trailing NULLs) - Mailing list pgsql-hackers

From Gokulakannan Somasundaram
Subject Re: Proposal for Null Bitmap Optimization(for Trailing NULLs)
Date
Msg-id 9362e74e0712170002h25c5249ev43831f80e1d475af@mail.gmail.com
Whole thread Raw
In response to Proposal for Null Bitmap Optimization(for Trailing NULLs)  ("Gokulakannan Somasundaram" <gokul007@gmail.com>)
List pgsql-hackers
We can also implement the same for index tuples.....


On Dec 17, 2007 1:10 PM, Gokulakannan Somasundaram <gokul007@gmail.com> wrote:
Hi,
    Currently we check for the existence of NULL values in the tuple and we set the has_null flag. If the has_null flag is present, the tuple will be storing a null bitmap. What i propose is

a) By modifying the functions, heap_form_tuple and heap_fill_tuple, we can check whether all the nulls are trailing nulls. If all the nulls are trailing nulls, then we will not set the has_null flag and we will not have the null bitmap with the tuple.

b) While selecting the tuple, we will check whether the tuple offset equals / exceeds the length of the tuple and then mark the remaining attributes of the tuple as null. To be exact, we need to modify the slot_deform_tuple in order to achieve the same.

This may not give huge performance benefits, but as you may know, it will help is reducing the disk footprint.


Expecting your comments..

--
Thanks,
Gokul.
CertoSQL Project,
Allied Solution Group.
(www.alliedgroups.com)



--
Thanks,
Gokul.
CertoSQL Project,
Allied Solution Group.
(www.alliedgroups.com)

pgsql-hackers by date:

Previous
From: "Gokulakannan Somasundaram"
Date:
Subject: Requesting clarification on Vacuuming/Freezing behaviour
Next
From: Heikki Linnakangas
Date:
Subject: Re: Requesting clarification on Vacuuming/Freezing behaviour