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: Andres Freund <andres@anarazel.de>, Michael Banck <mbanck@gmx.net>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Álvaro Herrera <alvherre@kurilemu.de>, melanieplageman@gmail.com, juanjo.santamaria@gmail.com
Date: 2026-01-06T05:41:16Z
Lists: pgsql-hackers 
On Thu, Jan 1, 2026 at 5:09 PM Soumya S Murali
<soumyamurali.work@gmail.com> wrote:
>
> Hi all,
>
> On Thu, Dec 18, 2025 at 5:49 AM Andres Freund <andres@anarazel.de> wrote:
> >
> > Hi,
> >
> > On 2025-12-01 16:48:56 +0530, Soumya S Murali wrote:
> > > This patch is an update after reworking the “checkpoint reason” changes as
> > > a standalone patch, separate from the pg_stat_checkpointer additions as
> > > suggested [1].

This kind of information already seems to be included in the
checkpoint starting log message, for example:

    LOG:  checkpoint starting: fast force wait

Why do you want to include essentially the same information in the
checkpoint ending log message as well?

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.