| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Brown <kevin(at)sysexperts(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Detecting corrupted pages earlier |
| Date: | 2003-02-18 15:21:57 |
| Message-ID: | 23593.1045581717@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kevin Brown <kevin(at)sysexperts(dot)com> writes:
> Tom Lane wrote:
>> The cases I've been able to study look like the header and a lot of the
>> following page data have been overwritten with garbage --- when it made
>> any sense at all, it looked like the contents of non-Postgres files (eg,
>> plain text), which is why I mentioned the possibility of disks writing
>> data to the wrong sector.
> That also sounds suspiciously like the behavior of certain filesystems
> (Reiserfs, for one) after a crash when the filesystem prior to the
> crash was highly active with writes.
Isn't reiserfs supposed to be more crash-resistant than ext2, rather
than less so?
> Had the sites that reported this
> experienced OS crashes or power interruptions?
Can't recall whether they admitted to such or not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2003-02-18 15:25:59 | Re: FW: Changing the default configuration (was Re: |
| Previous Message | Christopher Kings-Lynne | 2003-02-18 15:03:17 | Re: Non-colliding auto generated names |