Re: WAL consistency check facility

Kuntal Ghosh wrote:
> Thanks a lot.
>
> I just want to mention the situation where I was getting the
> speculative token related inconsistency.
>
> ItemPointer in backup page from master:
> LOG: ItemPointer BlockNumber: 1 OffsetNumber:65534 Speculative: true
> CONTEXT: xlog redo at 0/127F4A48 for Heap/INSERT+INIT: off 1
>
> ItemPointer in current page from slave after redo:
> LOG: ItemPointer BlockNumber: 0 OffsetNumber:1 Speculative: false
> CONTEXT: xlog redo at 0/127F4A48 for Heap/INSERT+INIT: off 1
>
> As the block numbers are different, I was getting the following warning:
> WARNING: Inconsistent page (at byte 8166) found for record
> 0/127F4A48, rel 1663/16384/16946, forknum 0, blkno 0, Backup Page
> Header : (pd_lower: 28 pd_upper: 8152 pd_special: 8192) Current Page
> Header: (pd_lower: 28 pd_upper: 8152 pd_special: 8192)
> CONTEXT: xlog redo at 0/127F4A48 for Heap/INSERT+INIT: off 1
>
> In heap_xlog_insert, t_ctid is always set to blkno and xlrec->offnum.
> I think this is why I was getting the above warning.

Umm, really? Then perhaps this *is* a bug. Peter?

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services