| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | "'Zeugswetter Andreas SB'" <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: heap page corruption not easy |
| Date: | 2000-12-19 23:48:14 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D3204@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > The point is, that the heap page is only modified in
> > > places that were previously empty (except header).
> > > All previous row data stays exactly in the same place.
> > > Thus if a page is only partly written
> > > (any order of page segments) only a new row is affected.
> >
> > Exception: PageRepairFragmentation() and PageIndexTupleDelete() are
> > called during vacuum - they change layout of tuples.
> >
>
> Is it guaranteed that the result of PageRepairFragmentation()
> has already been written to disk when tuple movement is logged ?
No.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Vixie | 2000-12-20 00:06:35 | Re: performance modality in 7.1 for large text attributes? |
| Previous Message | Peter Eisentraut | 2000-12-19 23:12:11 | Re: Generating HISTORY file |