AW: heap page corruption not easy

Поиск
Список
Период
Сортировка
От Zeugswetter Andreas SB
Тема AW: heap page corruption not easy
Дата
Msg-id 11C1E6749A55D411A9670001FA68796336818C@sdexcsrv1.f000.d0188.sd.spardat.at
обсуждение исходный текст
Список pgsql-hackers
> > The only source of serious problems is thus a bogus write of a page
> > segment (100 bytes ok 412 bytes chunk actually written to disk),
> > but this case is imho sufficiently guarded or at least detected
> > by disk hardware. 
> 
> With full page logging after checkpoint we would be safe from this
> case...

> Comments?
> 
> - full page backup on first after checkpoint modification

I guess you are right, especially since it solves above and index.
The "physical log" solution sounds a lot simpler and more robust
(I didn't know you use PageAddItem, sounds genially simple :-)

But we should probably try to do checkpoints less frequently by default, 
like every 20 min to avoid too much phys log.

Andreas


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

Предыдущее
От: "Steve Howe"
Дата:
Сообщение: OID Implicit limit
Следующее
От: Mathijs Brands
Дата:
Сообщение: Re: Re: [SQL] PostgreSQL crashes on me :(