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

From Florian Weimer
Subject Re: Block-level CRC checks
Date
Msg-id 82ocmiu4ao.fsf@mid.bfk.de
Whole thread Raw
In response to Re: Block-level CRC checks  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Block-level CRC checks  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
* Simon Riggs:

> * Put all hint bits in the block header to allow them to be excluded
> more easily from CRC checking. If we used 3 more bits from
> ItemIdData.lp_len (limiting tuple length to 4096) then we could store
> some hints in the item pointer. HEAP_XMIN_INVALID can be stored as
> LP_DEAD, since that will happen very quickly anyway.

What about putting the whole visibility information out-of-line, into
its own B-tree, indexed by page number?

--
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CommitFest status/management
Next
From: "Kevin Grittner"
Date:
Subject: Re: Deleted WAL files held open by backends in Linux