Re: Return value of XLogInsertRecord() for XLOG_SWITCH record

From: ZizhuanLiu X-MAN <44973863(at)qq(dot)com>
To: rring0727 <rring0727(at)gmail(dot)com>, cca5507 <cca5507(at)qq(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Return value of XLogInsertRecord() for XLOG_SWITCH record
Date: 2026-06-14 14:37:58
Message-ID: tencent_C26B62ED5BC2129C9AA2F10B9EA30D8DD605@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

rebase v4.

Early v2/v3 only fixed the page-cross judgment condition, but still retained duplicated
EndPos calculation logic. v4 refactors ReserveXLogSwitch to compute standard EndPos
once and reuse it, eliminating redundant code fundamentally.

All behavior remains identical to v2/v3 after fix; v4 just unifies the calculation
point without changing runtime logic.


ZizhuanLiu X-MAN
44973863(at)qq(dot)com

Attachment Content-Type Size
v4-0001-Keep-the-return-value-of-XLogInsertRecord-for-XLO.patch application/octet-stream 3.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ken Hibino 2026-06-14 14:48:27 [PATCH v1] Fix typo in InitWalRecovery() comment
Previous Message ZizhuanLiu X-MAN 2026-06-14 12:46:24 Re: Add ParameterDescription message to libpq frontend long message types