Re: [HACKERS] [PATCHES] wal_checksum = on (default) | off
Вложения
В списке pgsql-patches по дате отправления:
| От | Martijn van Oosterhout |
|---|---|
| Тема | Re: [HACKERS] [PATCHES] wal_checksum = on (default) | off |
| Дата | |
| Msg-id | 20070112100928.GA6589@svana.org обсуждение исходный текст |
| Ответ на | Re: [HACKERS] [PATCHES] wal_checksum = on (default) | off ("Simon Riggs" <simon@2ndquadrant.com>) |
| Список | pgsql-patches |
On Thu, Jan 11, 2007 at 11:10:38PM +0000, Simon Riggs wrote: > On Thu, 2007-01-11 at 17:06 +0000, Gregory Stark wrote: > > Having a CRC in WAL but not in the heap seems kind of pointless. > > Yes... > > > If your > > hardware is unreliable the corruption could anywhere. > > Agreed. I thought the point was that the WAL protects against unexpected power failure, that sort of thing. In that situation, the memory is the first to be corrupted, and an active DMA transfer will thus be corrupted also. We don't need to worry about the data, because the WAL is known to be accurate. The WAL does not protect against random data corruption, in normal operation it is never read. If we want to detect random corruption, we'd need checksum everywhere, yes. But that's not the goal here. Have a nice day, -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to litigate.
В списке pgsql-patches по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера