Re: [GENERAL] Undetected corruption of table files

From: Decibel! <decibel(at)decibel(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] Undetected corruption of table files
Date: 2007-08-31 21:17:50
Message-ID: 20070831211750.GJ38801@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Fri, Aug 31, 2007 at 03:11:29PM -0400, Tom Lane wrote:
> Decibel! <decibel(at)decibel(dot)org> writes:
> > Even if we don't care about folks running on suspect hardware, having a
> > CRC would make it far more reasonable to recommend full_page_writes=3Doff.
>
> This argument seems ridiculous. Finding out that you have corrupt data
> is no substitute for not having corrupt data.

Of course. But how will you discover you have corrupt data if there's no
mechanism to detect it?
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Davis 2007-08-31 21:40:08 Re: URGENT: Whole DB down ("no space left on device")
Previous Message Jeff Davis 2007-08-31 21:11:22 Re: auditing in postgresql

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian G. Pflug 2007-08-31 22:02:26 Re: [PATCH] Lazy xid assingment V2
Previous Message Tom Lane 2007-08-31 21:10:41 Re: [PATCH] Lazy xid assingment V2