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

Re: Block-level CRC checks

From: Florian Weimer <fweimer(at)bfk(dot)de>
To: Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>
Cc: Aidan Van Dyk <aidan(at)highrise(dot)ca>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Brian Hurt <bhurt(at)janestcapital(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Block-level CRC checks
Date: 2008-10-31 10:21:21
Message-ID: 824p2tawv2.fsf@mid.bfk.de (view raw or flat)
Thread:
Lists: pgsql-hackers
* Greg Stark:

> Wal logged changes are safe because of full_page_writes. Hint bits are
> safe because either the old or the new value will be on disk and we
> don't care which.

Is this really true with all disks?  IBM's DTLA disks didn't behave
that way (an interrupted write could zero a sector), and I think the
text book algorithms don't assume this behavior, either.

-- 
Florian Weimer                <fweimer(at)bfk(dot)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

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2008-10-31 10:53:01
Subject: Re: BufferAccessStrategy for bulk insert
Previous:From: KaiGai KoheiDate: 2008-10-31 09:34:02
Subject: Updates of SE-PostgreSQL 8.4devel patches (r1168)

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