| From: | "movead(dot)li(at)highgo(dot)ca" <movead(dot)li(at)highgo(dot)ca> |
|---|---|
| To: | Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | andres <andres(at)anarazel(dot)de>, michael <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, ahsan(dot)hadi <ahsan(dot)hadi(at)highgo(dot)ca> |
| Subject: | Re: Wrong statistics for size of XLOG_SWITCH during pg_waldump. |
| Date: | 2020-10-16 09:39:58 |
| Message-ID: | 2020101617395691465546@highgo.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>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
| Attachment | Content-Type | Size |
|---|---|---|
| fix_waldump_size_for_wal_switch_v5.patch | application/octet-stream | 4.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-10-16 10:26:51 | Re: Parallel INSERT (INTO ... SELECT ...) |
| Previous Message | Ashutosh Bapat | 2020-10-16 09:33:25 | Re: Enumize logical replication message actions |