Horton
Menu

Re: [PATCH] Expose checkpoint reason to completion log messages.

Fujii Masao <masao.fujii@gmail.com>

View thread
From: Fujii Masao <masao.fujii@gmail.com>
To: Soumya S Murali <soumyamurali.work@gmail.com>
Cc: Michael Banck <mbanck@gmx.net>, VASUKI M <vasukianand0119@gmail.com>, Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Álvaro Herrera <alvherre@kurilemu.de>, melanieplageman@gmail.com, juanjo.santamaria@gmail.com
Date: 2026-02-19T14:57:24Z
Lists: pgsql-hackers 
On Tue, Feb 17, 2026 at 7:47 PM Soumya S Murali
<soumyamurali.work@gmail.com> wrote:
> Thank you very much for refining the implementation and simplifying
> the flag construction logic using snprintf(). I have reviewed the
> committed changes and verified that the formatting and behavior are
> consistent and correct. The updated approach is clear and aligns well
> with PostgreSQL coding style. I also appreciate the improvements made
> to the commit message as it clearly explains the motivation and makes
> the change easy to understand in context.

I've pushed the patch. Thanks!

Regards,

-- 
Fujii Masao

Commits

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

  1. Log checkpoint request flags in checkpoint completion messages.