Be clear about what log_checkpoints emits in the documentation
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t45279psql -h localhost -U postgresBuilt from patchset v1 (message #1), October 06, 2026 at 11:55 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t45279_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t45279_1 && git checkout t45279_1Patchset v1 (message #1) is on t45279_1
Hi,
Currently the documentation of the log_checkpoints GUC says the following:
Some statistics are included in the log messages, including the number
of buffers written and the time spent writing them.
Usage of the word "Some" makes it a vague statement. Why can't we just
be clear about what statistics the log_checkpoints GUC can emit, like
the attached patch?
Thoughts?
Regards,
Bharath Rupireddy.
At Thu, 23 Dec 2021 20:56:22 +0530, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> wrote in
Hi,
Currently the documentation of the log_checkpoints GUC says the following:
Some statistics are included in the log messages, including the number
of buffers written and the time spent writing them.Usage of the word "Some" makes it a vague statement. Why can't we just
be clear about what statistics the log_checkpoints GUC can emit, like
the attached patch?Thoughts?
It seems like simply a maintenance burden of documentation since it
doesn't add any further detail of any item in a checkpoint log
message. But I'm not sure we want detailed explanations for them and
it seems to me we deliberately never explained the detail of any log
messages.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
On Fri, Dec 24, 2021 at 11:30 AM Kyotaro Horiguchi
<horikyota.ntt@gmail.com> wrote:
At Thu, 23 Dec 2021 20:56:22 +0530, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> wrote in
Hi,
Currently the documentation of the log_checkpoints GUC says the following:
Some statistics are included in the log messages, including the number
of buffers written and the time spent writing them.Usage of the word "Some" makes it a vague statement. Why can't we just
be clear about what statistics the log_checkpoints GUC can emit, like
the attached patch?Thoughts?
It seems like simply a maintenance burden of documentation since it
doesn't add any further detail of any item in a checkpoint log
message. But I'm not sure we want detailed explanations for them and
it seems to me we deliberately never explained the detail of any log
messages.
Agreed. "Some statistics" can cover whatever existing and newly added
stuff, if any. Let it be that way.
Regards,
Bharath Rupireddy.