* Alban Hertroys:
> If you have a "proper" production database server, your memory has
> error checking, and your RAID controller has something of the kind
> as well.
To my knowledge, no readily available controller performs validation
on reads (not even for RAID-1 or RAID-10, where it would be p
At 11:48 PM 8/27/2007, Trevor Talbot wrote:
On 8/27/07, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
> On 8/27/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> > that and the lack of evidence that they'd actually gain anything
>
> I find it somewhat ironic that PostgreSQL strives to be fairly
> non-corrup
On Mon, Aug 27, 2007 at 12:08:17PM -0400, Jonah H. Harris wrote:
> On 8/27/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> > Indeed. In fact, the most likely implementation of this (refuse to do
> > anything with a page with a bad CRC) would be a net loss from that
> > standpoint, because you couldn't g
On 8/27/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> Indeed. In fact, the most likely implementation of this (refuse to do
> anything with a page with a bad CRC) would be a net loss from that
> standpoint, because you couldn't get *any* data out of a page, even if
> only part of it had been zapped.
"Trevor Talbot" <[EMAIL PROTECTED]> writes:
> On 8/27/07, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
>> I find it somewhat ironic that PostgreSQL strives to be fairly
>> non-corruptable, yet has no way to detect a corrupted page.
> But how does detecting a corrupted data page gain you any durabili
Jonah H. Harris wrote:
> On 8/27/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>> that and the lack of evidence that they'd actually gain anything
>
> I find it somewhat ironic that PostgreSQL strives to be fairly
> non-corruptable, yet has no way to detect a corrupted page. The only
> reason for not h
"Tom Lane" <[EMAIL PROTECTED]> writes:
> "Albe Laurenz" <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
Would it be an option to have a checksum somewhere in each
data block that is verified upon read?
>
>>> That's been proposed before and rejected before. See the archives ...
>
>> I sea
On 8/27/07, Jonah H. Harris <[EMAIL PROTECTED]> wrote:
> On 8/27/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> > that and the lack of evidence that they'd actually gain anything
>
> I find it somewhat ironic that PostgreSQL strives to be fairly
> non-corruptable, yet has no way to detect a corrupted pa
On 8/27/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> that and the lack of evidence that they'd actually gain anything
I find it somewhat ironic that PostgreSQL strives to be fairly
non-corruptable, yet has no way to detect a corrupted page. The only
reason for not having CRCs is because it will slow
"Albe Laurenz" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>>> Would it be an option to have a checksum somewhere in each
>>> data block that is verified upon read?
>> That's been proposed before and rejected before. See the archives ...
> I searched for "checksum" and couldn't find it. Could
Tom Lane wrote:
>> Would it be an option to have a checksum somewhere in each
>> data block that is verified upon read?
>
> That's been proposed before and rejected before. See the archives ...
I searched for "checksum" and couldn't find it. Could someone
give me a pointer? I'm not talking about
"Albe Laurenz" <[EMAIL PROTECTED]> writes:
> Would it be an option to have a checksum somewhere in each
> data block that is verified upon read?
That's been proposed before and rejected before. See the archives ...
regards, tom lane
---(end of bro
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.
"Albe Laurenz" <[EMAIL PROTECTED]> 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 var
I am slightly worried that corruption of data files may
remain undetected in PostgreSQL.
As an experiment, I created a simple table with a primary key
index and inserted a couple of rows. The corresponding data file
is 1 page = 8K long.
Now when I stop the server, zero out the data file with
dd i
15 matches
Mail list logo
