Horton
Menu

Re: Return value of XLogInsertRecord() for XLOG_SWITCH record

ZizhuanLiu X-MAN <44973863@qq.com>

View thread
From: ZizhuanLiu X-MAN <44973863@qq.com>
To: ZizhuanLiu X-MAN <44973863@qq.com>, rring0727 <rring0727@gmail.com>, cca5507 <cca5507@qq.com>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-06-15T05:27:06Z
Lists: pgsql-hackers

Attachments

Let us rebase v3 first .

regards,
--
ZizhuanLiu (X-MAN) 
44973863@qq.com


>Original
>From: ZizhuanLiu X-MAN <44973863@qq.com>
>Date: 2026-06-14 22:37
>To: rring0727 <rring0727@gmail.com>, cca5507 <cca5507@qq.com>
>Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.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@qq.com

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Undo thinko in commit e78d1d6d4.

  2. Fix orphaned processes when startup process fails during PM_STARTUP