| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | decibel <decibel(at)decibel(dot)org>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, jd(at)commandprompt(dot)com, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Block-level CRC checks |
| Date: | 2009-12-04 12:57:05 |
| Message-ID: | 1259931425.13774.38304.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2009-12-04 at 07:54 -0500, Bruce Momjian wrote:
> > I should also point out that removing 4 bits from the tuple header would
> > allow us to get rid of t_infomask2, reducing tuple length by a further 2
> > bytes.
>
> Wow, that is a nice win. Does alignment allow us to actually use that
> space?
It would mean that tables up to 24 columns wide would still be 24 bytes
wide, whereas >8 columns now has to fit in 32 bytes. So in practical
terms most tables would benefit in your average database.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-12-04 13:00:13 | Re: Block-level CRC checks |
| Previous Message | Bruce Momjian | 2009-12-04 12:54:51 | Re: Block-level CRC checks |