| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex Stapleton <alexs(at)advfn(dot)com> |
| 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:07:37 |
| Message-ID: | 19144.1130425657@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-10-27 15:10:11 | Re: Need help with INOUT mis-understanding |
| Previous Message | Carlos Oliva | 2005-10-27 14:30:07 | pg_dump fails when it gets to table containing bytea |