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

From Hiroshi Inoue
Subject Re: heap page corruption not easy
Date
Msg-id 3A3EB29B.AAAD7E3D@tpf.co.jp
Whole thread Raw
In response to RE: heap page corruption not easy  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
List pgsql-hackers
"Mikheev, Vadim" wrote:
> 
> > 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 ?

Regards.
Hiroshi Inoue


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Who is a maintainer of GiST code ?
Next
From: Ryan Kirkpatrick
Date:
Subject: Re: [DOCS] 7.1 features list