Re: Why database is corrupted after re-booting

From: Alex Stapleton <alexs(at)advfn(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: snacktime <snacktime(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why database is corrupted after re-booting
Date: 2005-10-27 15:14:22
Message-ID: BAD7B67D-6341-458D-9FC4-08A6FE14FA58@advfn.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On 27 Oct 2005, at 16:07, Tom Lane wrote:

> Alex Stapleton <alexs(at)advfn(dot)com> writes:
>
>> The system RAM won't usually be supported by any batteries though, so
>> it will go crazy, copy corrupt data to the DIMMs on the RAID
>> controller, which then will refuse to write it to the disk until the
>> power comes up, and then write the bad data to the drive surely?
>>
>
> Not in competently designed hardware. The system should shut down
> completely the instant the power supply's outputs go out of spec,
> which will be before the logic components actually start to
> malfunction.
>
> This is not to say that cheap consumer-grade PCs are competently
> designed ;-) but the issue was a solved problem when I was a
> practicing EE, and that was a long time ago.

lol, iirc it was an middle aged piece of random dell equipment. They
seem to be getting progressively less awful these days so maybe it
was just that particular model. I may have to do some evil tests
using glass fuses and hammers (and rubber gloves).......

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-10-27 15:22:39 Re: pg_dump fails when it gets to table containing bytea
Previous Message Tom Lane 2005-10-27 15:10:11 Re: Need help with INOUT mis-understanding