Re: Undetected corruption of table files

From: "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>
To: "Tom Lane *EXTERN*" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Undetected corruption of table files
Date: 2007-08-24 07:57:41
Message-ID: D960CB61B694CF459DCFB4B0128514C218DA78@exadv11.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Tom Lane wrote:
>> - Shouldn't there be an error, some kind of 'missing magic
>> number' or similar, when a table file consists of only
>> zeros?
>
> The particular case of an all-zeroes page is specifically allowed,
> and has to be because it's a valid transient state in various
> scenarios.

I see, that was a pathological case.

>> - Wouldn't it be desirable to have some means to verify the
>> integrity of a table file or a whole database?
>
> SELECT * usually does reasonably well at that.

Would it be an option to have a checksum somewhere in each
data block that is verified upon read?

Would this be a lot of work to add? I'd be willing to try it
if it is desirable and feasible.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2007-08-24 08:09:52 Re: PostgreSQL vs Firebird feature comparison finished
Previous Message Hannes Dorbath 2007-08-24 07:20:52 Re: Apache + PHP + Postgres Interaction

Browse pgsql-hackers by date

  From Date Subject
Next Message Anton 2007-08-24 08:53:05 partitioned table and ORDER BY indexed_field DESC LIMIT 1
Previous Message Richard Huxton 2007-08-24 07:27:30 Re: Segmentation fault using digest from pg_crypto