Skip site navigation (1) Skip section navigation (2)

Re: Block-level CRC checks

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
Cc: Aidan Van Dyk <aidan(at)highrise(dot)ca>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql(at)mohawksoft(dot)com, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, "Decibel!" <decibel(at)decibel(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Block-level CRC checks
Date: 2008-10-02 06:35:25
Message-ID: 48E46BAD.6010501@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Jonah H. Harris wrote:
> Rather than potentially letting this slide past 8.4, I threw together
> an extremely quick-hack patch at the smgr-layer for block-level
> checksums.

One hard problem is how to deal with torn pages with non-WAL-logged 
changes. Like heap hint bit updates, killing tuples in index pages 
during a scan, and the new FSM pages.

Currently, a torn page when writing a hint-bit-updated page doesn't 
matter, but it would break the checksum.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-hackers by date

Next:From: Florian WeimerDate: 2008-10-02 07:41:47
Subject: Re: Block-level CRC checks
Previous:From: Jonah H. HarrisDate: 2008-10-02 05:59:16
Subject: Re: Block-level CRC checks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group