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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Soumya S Murali <soumyamurali(dot)work(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Michael Banck <mbanck(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, melanieplageman(at)gmail(dot)com, juanjo(dot)santamaria(at)gmail(dot)com
Subject: Re: [PATCH] Expose checkpoint reason to completion log messages.
Date: 2026-01-06 05:41:16
Message-ID: CAHGQGwFzR=1EwefWGVNF5GaOMsNkWZZ9oJMXiwO3x8AhjUTqsQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 1, 2026 at 5:09 PM Soumya S Murali
<soumyamurali(dot)work(at)gmail(dot)com> wrote:
>
> Hi all,
>
> On Thu, Dec 18, 2025 at 5:49 AM Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2026-01-06 05:42:59 Re: Implement waiting for wal lsn replay: reloaded
Previous Message Michael Paquier 2026-01-06 05:38:06 Re: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE