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

From Tom Lane
Subject Re: Block-level CRC checks
Date
Msg-id 27210.1226677917@sss.pgh.pa.us
Whole thread Raw
In response to Re: Block-level CRC checks  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: Block-level CRC checks  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-hackers
Martijn van Oosterhout <kleptog@svana.org> writes:
> But I understand the problem is that you want to continue in the face
> of torn pages, something which is AFAICS ambitious. At least MS-SQL
> just blows up on a torn page, havn't found results for other
> databases...

I don't think it's too "ambitious" to demand that this patch preserve
a behavior we have today.

In fact, if the patch were to break torn-page handling, it would be
100% likely to be a net *decrease* in system reliability.  It would add
detection of a situation that is not supposed to happen (ie, storage
system fails to return the same data it stored) at the cost of breaking
one's database when the storage system acts as it's expected and
documented to in a routine power-loss situation.

So no, I don't care that MSSQL is unable to handle this.  This patch
must, or it doesn't go in.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Simple postgresql.conf wizard
Next
From: "Jonah H. Harris"
Date:
Subject: Re: Simple postgresql.conf wizard