RE: heap page corruption not easy - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: heap page corruption not easy
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D3204@sectorbase1.sectorbase.com
Whole thread Raw
In response to heap page corruption not easy  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List 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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Re: Table name scope (was Re: [BUGS] Outer joins aren't working with views)
Next
From: "Mikheev, Vadim"
Date:
Subject: RE: Who is a maintainer of GiST code ?