Re: Block-level CRC checks - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Block-level CRC checks
Date
Msg-id 1259931425.13774.38304.camel@ebony
Whole thread Raw
In response to Re: Block-level CRC checks  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Block-level CRC checks  (Greg Stark <gsstark@mit.edu>)
List 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



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Block-level CRC checks
Next
From: Simon Riggs
Date:
Subject: Re: Block-level CRC checks