| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-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 | Content-Type | Size |
|---|---|---|
| trailing_nulls.patch.gz | application/x-gzip | 3.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2007-12-20 10:19:29 | Re: pgwin32_open returning EINVAL |
| Previous Message | Magnus Hagander | 2007-12-20 08:32:38 | Re: pgwin32_open returning EINVAL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Urbański | 2007-12-20 16:48:32 | typo in func.sgml |
| Previous Message | Hiroshi Saito | 2007-12-20 01:02:24 | Re: win32.mak patch |