Thanks for taking a look on this. At Fri, 4 Dec 2020 04:20:47 +0000, <shinya11.k...@nttdata.com> wrote in > When I execute pg_waldump, I found that XLOG/SWITCH_JUNK appears twice. > Is this problem solved by the way of correcting the previously discussed > Transaction/COMMIT? > > $ ../bin/pg_waldump --stats=record ../data/pg_wal/000000010000000000000001 > Type N (%) Record > size (%) FPI size (%) Combined size (%) > ---- - --- > ----------- --- -------- --- ------------- > --- .. > XLOG/SWITCH_JUNK 0 ( 0.00) > 0 ( 0.00) 0 ( 0.00) 0 ( 0.00) ... > XLOG/SWITCH_JUNK 0 ( 0.00) > 0 ( 0.00) 0 ( 0.00) 0 ( 0.00)
Yeah, that's because of XLogDumpDisplayStats forgets to consider ri (rmgr id) when showing the lines. If there's a record with info = 0x04 for other resources than RM_XLOG_ID, the spurious line is shown. The first one is for XLOG_HEAP2_VISIBLE and the latter is for XLOG_HEAP_HOT_UPDATE, that is, both of which are not for XLOG_SWITCH.. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
