| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Trevor Talbot" <quension(at)gmail(dot)com> |
| Cc: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Undetected corruption of table files |
| Date: | 2007-08-27 16:00:34 |
| Message-ID: | 1433.1188230434@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Trevor Talbot" <quension(at)gmail(dot)com> writes:
> On 8/27/07, Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com> 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 durability?
> All it means is that the platform underneath screwed up, and you've
> already *lost* durability. What do you do then?
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vivek Khera | 2007-08-27 16:01:10 | Re: Bigtime scaling of Postgresql (cluster and stuff I suppose) |
| Previous Message | Alban Hertroys | 2007-08-27 15:58:24 | Re: [HACKERS] Undetected corruption of table files |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-08-27 16:08:08 | Re: pgsql: Fix brain fade in DefineIndex(): it was continuing to access the |
| Previous Message | Alban Hertroys | 2007-08-27 15:58:24 | Re: [HACKERS] Undetected corruption of table files |