Request a Demo
Home   >   mailing lists

Re: [PATCH] Expose checkpoint reason to completion log messages. - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: [PATCH] Expose checkpoint reason to completion log messages.
Date
Msg-id CAHGQGwGXoai8-83p5x2FhHnu6LD=epsapa_RTTzM3RHShju3Jw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Expose checkpoint reason to completion log messages.  (VASUKI M <vasukianand0119@gmail.com>)
Responses Re: [PATCH] Expose checkpoint reason to completion log messages.
List pgsql-hackers
Tree view 
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
outwhat 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

pgsql-hackers by date:

Previous
From: Jakub Wartak
Date:
Subject: Re: failed NUMA pages inquiry status: Operation not permitted
Next
From: "Pavlo Golub"
Date:
Subject: Re[2]: [PATCH] Add pg_current_vxact_id() function to expose virtual transaction IDs