On Thu, Sep 8, 2016 at 1:20 PM, Michael Paquier <michael.paqu...@gmail.com> wrote: > >> 2. For BRIN/UPDATE+INIT, block numbers (in rm_tid[0]) are different in >> REVMAP page. This happens only for two cases. I'm not sure what the >> reason can be. > > Hm? This smells like a block reference bug. What are the cases you are > referring to? > Following is the only case where the backup page stored in the wal record and the current page after redo are not consistent.
test:BRIN using gmake-check Master ----------------------------------------- STATEMENT: VACUUM brintest; LOG: INSERT @ 0/59E1E0F8: - BRIN/UPDATE+INIT: heapBlk 100 pagesPerRange 1 old offnum 11, new offnum 1 Standby ---------------------------------------------- LOG: REDO @ 0/59E1B500; LSN 0/59E1E0F8: prev 0/59E17578; xid 0; len 14; blkref #0: rel 1663/16384/30556, blk 12; blkref #1: rel 1663/16384/30556, blk 1; blkref #2: rel 1663/16384/30556, blk 2 - BRIN/UPDATE+INIT: heapBlk 100 pagesPerRange 1 old offnum 11, new offnum 1 WARNING: Inconsistent page (at byte 26) found, rel 1663/16384/30556, forknum 0, blkno 1 CONTEXT: xlog redo at 0/59E1B500 for BRIN/UPDATE+INIT: heapBlk 100 pagesPerRange 1 old offnum 11, new offnum 1 thoughts? -- Thanks & Regards, Kuntal Ghosh EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
