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: VASUKI M <vasukianand0119@gmail.com>
Cc: Michael Banck <mbanck@gmx.net>, Soumya S Murali <soumyamurali.work@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-01-06T13:25:39Z
Lists: pgsql-hackers 
On Tue, Jan 6, 2026 at 8:09 PM VASUKI M <vasukianand0119@gmail.com> wrote:
>
> Yeah,the proposed idea makes sense to me,as users will almost see at the end of log messages it will be easy to find out what is the checkpoint reason.
> +1 for it.

If we do this, it would be better to keep the wording consistent between
the checkpoint starting and completion messages. For example,
the patch represents CHECKPOINT_FAST as "immediate",
while the checkpoint starting message uses "fast"; those should match.

I'm also wondering why this information is currently included only in
the checkpoint starting message. I tried to find any past discussion on this,
but couldn’t find one.

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.