Re: Protecting against unexpected zero-pages: proposal

Поиск
Список
Период
Сортировка
От Aidan Van Dyk
Тема Re: Protecting against unexpected zero-pages: proposal
Дата
Msg-id AANLkTi=JtCYr1eKXaCCV-h6H9noXWtfjsLs61uqXpH8q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Protecting against unexpected zero-pages: proposal  (Greg Stark <gsstark@mit.edu>)
Ответы Re: Protecting against unexpected zero-pages: proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Sun, Nov 7, 2010 at 1:04 AM, Greg Stark <gsstark@mit.edu> wrote:
> It does seem like this is kind of part and parcel of adding checksums
> to blocks. It's arguably kind of silly to add checksums to blocks but
> have an commonly produced bitpattern in corruption cases go
> undetected.

Getting back to the checksum debate (and this seems like a
semi-version of the checksum debate), now that we have forks, could we
easily add block checksumming to a fork?  IT would mean writing to 2
files but that shouldn't be a problem, because until the checkpoint is
done (and thus both writes), the full-page-write in WAL is going to
take precedence on recovery.

a.


--
Aidan Van Dyk                                             Create like a god,
aidan@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: W3C Specs: Web SQL
Следующее
От: Robert Haas
Дата:
Сообщение: Re: timestamp of the last replayed transaction