Re: [PATCH] Expose checkpoint timestamp and duration in pg_stat_checkpointer

From: Soumya S Murali <soumyamurali(dot)work(at)gmail(dot)com>
To: Michael Banck <mbanck(at)gmx(dot)net>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, melanieplageman(at)gmail(dot)com, juanjo(dot)santamaria(at)gmail(dot)com
Subject: Re: [PATCH] Expose checkpoint timestamp and duration in pg_stat_checkpointer
Date: 2026-05-15 06:27:28
Message-ID: CAMtXxw9n=gOKYti2ekvPJ7tS7MQewgrkSmO8do-A+KwXXdoLLw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi all,

I would like to revive this patch, as the discussion has been inactive
for some time. Based on earlier feedback, I wanted to briefly restate
the motivation of exposing the last checkpoint duration and timestamp
that provides a direct signal of recent checkpoint behavior, which is
currently hard to infer reliably from cumulative statistics especially
when multiple checkpoints occur between monitoring intervals. This is
intended to complement existing cumulative fields, not replacing them
and helps detect sudden spikes in checkpoint duration or unusually
frequent checkpoints more easily.
If there is interest in this direction, I can rebase the patch on
current HEAD and incorporate any suggested changes.
Looking forward to more feedback and thoughts on this.

Regards,
Soumya

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2026-05-15 06:33:53 Re: Re-add recently-removed tests for ltree and intarray
Previous Message Michael Paquier 2026-05-15 06:22:12 Simplify signature of ProcessStartupPacket()