Re: [HACKERS] Undetected corruption of table files
| От | Tom Lane |
|---|---|
| Тема | Re: [HACKERS] Undetected corruption of table files |
| Дата | |
| Msg-id | 1433.1188230434@sss.pgh.pa.us обсуждение |
| Ответ на | Re: [HACKERS] Undetected corruption of table files ("Trevor Talbot" <quension@gmail.com>) |
| Ответы |
Re: [HACKERS] Undetected corruption of table files
|
| Список | pgsql-general |
"Trevor Talbot" <quension@gmail.com> writes:
> On 8/27/07, Jonah H. Harris <jonah.harris@gmail.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
В списке pgsql-general по дате отправления: