Re: pg_resetwal.c: duplicate '0' in hex character set for -l option validation - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_resetwal.c: duplicate '0' in hex character set for -l option validation
Date
Msg-id aai-8buoS7nr1uzX@paquier.xyz
Whole thread Raw
In response to Re: pg_resetwal.c: duplicate '0' in hex character set for -l option validation  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: pg_resetwal.c: duplicate '0' in hex character set for -l option validation
List pgsql-hackers
On Wed, Mar 04, 2026 at 09:16:12AM +0800, Chao Li wrote:
> In your recent batch commit
> 462fe0ff6215ae222fc866af621e4b86462289b1, I noticed that nobody was
> credited.

Please note that I have discussed this question with others offline,
hence the delay in my reply.

> Does this mean that people who report typo-like problems
> will no longer be credited?

Yes, that was on purpose.  We have seen a large increase of these
trivial patches to pgsql-hackers lately for some reason.  Maybe it is
LLMs or scanners or just a lot of new people with fresh eyes looking
at the code.  It started to get tedious to process them one by one,
and we discussed among committers if we could have a more lightweight
process for them.  As an experiment, I started to collect all such
changes into these larger batches.  Not crediting the reporters is
part of the experiment; tracking credit for trivial typo fixes is
hardly worth the effort, skipping that makes the process less
time-consuming.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Change default value of default_toast_compression to "lz4", when
Next
From:
Date:
Subject: RE: [BUG + PATCH] DSA pagemap out-of-bounds in make_new_segment odd-sized path