Re: Wrong statistics for size of XLOG_SWITCH during pg_waldump.
movead.li@highgo.ca <movead.li@highgo.ca>
From: "movead.li@highgo.ca" <movead.li@highgo.ca>
To: Horiguchi <horikyota.ntt@gmail.com>
Cc: andres <andres@anarazel.de>, michael <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@postgresql.org>, ahsan.hadi <ahsan.hadi@highgo.ca>
Date: 2020-10-16T09:39:58Z
Lists: pgsql-hackers
Attachments
- fix_waldump_size_for_wal_switch_v5.patch (application/octet-stream) patch v5
>It looks to me "We can know that length by subtracting the LSN of >XLOG_SWITCH from the next record's LSN so it doesn't add any >information." Sorry,maybe I miss this before. But I think it will be better to show it clearly. >So the length of <EMPTY> in this case is: > >LOC(SEG A+1) - ReadRecPtr - LEN(short header) - LEN(XLOG_SWITCH) Thanks, I should not have missed this and fixed. Regards, Highgo Software (Canada/China/Pakistan) URL : www.highgo.ca EMAIL: mailto:movead(dot)li(at)highgo(dot)ca
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