| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Gokulakannan Somasundaram <gokul007(at)gmail(dot)com> |
| Cc: | pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal for Null Bitmap Optimization(for Trailing NULLs) |
| Date: | 2007-12-17 09:58:59 |
| Message-ID: | 1197885539.12912.99.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Mon, 2007-12-17 at 13:10 +0530, Gokulakannan Somasundaram wrote:
> 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
Will this work for ALTER TABLE when adding and dropping columns?
Another idea is to store the bitmap from the first nullable column.
Some of these ideas have been discussed before, so I would check the
archives thoroughly. Most everything has if you look closely enough.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | peter.trautmeier | 2007-12-17 11:45:51 | ecxt_scantuple has wrong TupleDesc |
| Previous Message | Gregory Stark | 2007-12-17 09:23:44 | Re: Proposal for Null Bitmap Optimization(for Trailing NULLs) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gokulakannan Somasundaram | 2007-12-17 13:23:25 | Re: Proposal for Null Bitmap Optimization(for Trailing NULLs) |
| Previous Message | Gregory Stark | 2007-12-17 09:23:44 | Re: Proposal for Null Bitmap Optimization(for Trailing NULLs) |