Re: Fix wrong log in pgstat_report_checksum_failures_in_db()

From: wangpeng <215722532(at)qq(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Fix wrong log in pgstat_report_checksum_failures_in_db()
Date: 2026-02-12 00:59:13
Message-ID: tencent_A089097AA1B2012050EE16FA55584F4F7309@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
v2-0001-Fix-wrong-log-in-pgstat_report_checksum_failures.patch text/plain 920 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-02-12 01:07:08 Re: Is it OK to perform logging while holding a LWLock?
Previous Message Chao Li 2026-02-12 00:37:54 Odd usage of errmsg_internal in bufmgr.c