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-15 07:18:43
Message-ID: tencent_66C1D28CDABC71031EA1CD8EB67DE2FFFB05@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rebase v4 .

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

>Original
>From: ZizhuanLiu X-MAN <44973863(at)qq(dot)com>
>Date: 2026-06-14 22:37
>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
>
>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.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Tatsuya Kawata 2026-06-15 06:54:24 [PATCH] Change wait_time column of pg_stat_lock to double precision