Re: Wrong statistics for size of XLOG_SWITCH during pg_waldump.
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: movead.li@highgo.ca
Cc: pgsql-hackers@postgresql.org, ahsan.hadi@highgo.ca
Date: 2020-10-09T08:46:58Z
Lists: pgsql-hackers
At Fri, 9 Oct 2020 13:41:25 +0800, "movead.li@highgo.ca" <movead.li@highgo.ca> wrote in > Hello hackers, > > We know that pg_waldump can statistics size for every kind of records. When I use > the feature I find it misses some size for XLOG_SWITCH records. When a user does > a pg_wal_switch(), then postgres will discard the remaining size in the current wal > segment, and the pg_waldump tool misses the discard size. > > I think it will be better if pg_waldump can show the matter, so I make a patch > which regards the discard size as a part of XLOG_SWITCH record, it works if we > want to display the detail of wal records or the statistics, and patch attached. > > What's your opinion? I think that the length of the XLOG_SWITCH record is no other than 24 bytes. Just adding the padding? garbage bytes to that length doesn't seem the right thing to me. If we want pg_waldump to show that length somewhere, it could be shown at the end of that record explicitly: rmgr: XLOG len (rec/tot): 24/16776848, tx: 0, lsn: 0/02000148, prev 0/02000110, desc: SWITCH, trailing-bytes: 16776944 regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
-
pg_waldump: Fix bug in per-record statistics.
- e73068b0710b 9.6.22 landed
- 5386a8506d7d 10.17 landed
- 4a2627c41cfe 11.12 landed
- 4220e06f4c0c 12.7 landed
- 34279fd4fabd 13.3 landed
- 51893c846350 14.0 landed