From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Mikheev, Vadim'" <vmikheev(at)SECTORBASE(dot)COM> |
Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: heap page corruption not easy |
Date: | 2000-12-19 08:15:18 |
Message-ID: | 11C1E6749A55D411A9670001FA68796336818C@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Sébastien Bonnet | 2000-12-19 14:08:57 | libpq enhancement for multi-process application |
Previous Message | Thomas Lockhart | 2000-12-19 07:10:03 | Re: Re: Beos update |