Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Proposal for Null Bitmap Optimization(for TrailingNULLs)

From: "Gokulakannan Somasundaram" <gokul007(at)gmail(dot)com>
To: "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Subject: Re: [HACKERS] Proposal for Null Bitmap Optimization(for TrailingNULLs)
Date: 2007-12-20 08:36:49
Message-ID: 9362e74e0712200036l29081b1eq3ad0e815f07a3ee8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Thanks for the suggestions. I am re-submitting the patch in contextual diff
format.

As far as storage savings are concened, the patch claims whatever is stated.
I checked it by creating a table with 10 columns on a 32 bit machine. i
inserted 100,000 rows with trailing nulls and i observed savings of
400Kbytes.
I did a similar test for index and i found similar space saving.

I have tested regression in both 32 bit system and 64 bit system.

Please go through the patch and provide further suggestions.

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

Attachment: trailing_nulls.patch.gz
Description: application/x-gzip (3.4 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2007-12-20 10:19:29
Subject: Re: pgwin32_open returning EINVAL
Previous:From: Magnus HaganderDate: 2007-12-20 08:32:38
Subject: Re: pgwin32_open returning EINVAL

pgsql-patches by date

Next:From: Jan UrbaƄskiDate: 2007-12-20 16:48:32
Subject: typo in func.sgml
Previous:From: Hiroshi SaitoDate: 2007-12-20 01:02:24
Subject: Re: win32.mak patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group