Re: Fix wrong log in pgstat_report_checksum_failures_in_db()
wangpeng <215722532@qq.com>
From: wangpeng <215722532@qq.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2026-02-12T00:59:13Z
Lists: pgsql-hackers
Attachments
- v2-0001-Fix-wrong-log-in-pgstat_report_checksum_failures.patch (text/plain) patch v2-0001
Michael Paquier 写于 2026/2/11 19:06: > On Wed, Feb 11, 2026 at 05:22:27PM +0800, wangpeng wrote: > > The function pgstat_report_checksum_failures_in_db(), file > > pgstat_database.c, > > currently emits a log message referring to "conflicts", which seems wrong. > > As the function name suggesting, the log message should refer to "checksum > > failures". > > Right, that's strange. It looks like a copy-pasto, but I am not sure > from where. > > > - elog(WARNING, "could not report %d conflicts for DB %u", > > + elog(WARNING, "could not report %d checksum failures for DB %u", > > failurecount, dboid); > > We may as well use "for database" here. Let's improve it a bit more > while on it, even if it is not translated. > -- > Michael Thanks for your review. Updated "for DB" to "for database" in v2. Best regards, Wang Peng
Commits
-
Improve error message for checksum failures in pgstat_database.c
- 5b0e0c3d03eb 18.3 landed
- 775fc014156b 19 (unreleased) landed