| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)skype(dot)net> |
| Cc: | mark(at)mark(dot)mielke(dot)cc, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Pavan Deolasee <pavan(dot)deolasee(at)enterprisedb(dot)com>, Nikhil S <nikhil(dot)sontakke(at)enterprisedb(dot)com> |
| Subject: | Re: HOT for PostgreSQL 8.3 |
| Date: | 2007-02-13 09:21:35 |
| Message-ID: | 45D1831F.1080607@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing wrote:
>> But actually that 1 free byte in the header is not currently just waste
>> of space. If you have any nulls in your tuple, there's going to be a
>> null bitmap in addition to the header. 1 byte is conveniently enough to
>> store the null bitmap for a table with max 8 columns,
>
> Are we actually doing that ? I.E are null bitmaps really allocated in 1
> byte steps nowadays ?
Yes.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian G. Pflug | 2007-02-13 10:46:36 | Re: Foreign keys for non-default datatypes, redux |
| Previous Message | Magnus Hagander | 2007-02-13 09:13:21 | 8.1 stats issues on Win32 |