Re: Undetected corruption of table files

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

"Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> writes:
> - 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.

> - 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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Erik Jones 2007-08-23 17:14:43 Re: Argument type list
Previous Message Ned Lilly 2007-08-23 17:00:29 Re: reporting tools

Browse pgsql-hackers by date

  From Date Subject
Next Message Chuck McDevitt 2007-08-23 17:16:40 Re: SQL feature requests
Previous Message Ben Tilly 2007-08-23 16:57:16 Re: SQL feature requests