Re: [PATCH] Warn when io_min_workers exceeds io_max_workers

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Baji Shaik <baji.pgdev@gmail.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, tristan@partin.io, pgsql-hackers@lists.postgresql.org
Date: 2026-07-06T02:41:06Z
Lists: pgsql-hackers
On Tue, Jun 23, 2026 at 11:02:57AM -0500, Baji Shaik wrote:
> Thanks for the review.

This patch was still very noisy.  If running a bunch of reloads, we'd
still emit a WARNING all the time even if none of the bounds change.
This can be easily avoided: save the previous bound value before
ProcessConfigFile(), then recheck and proceed if one of the values has
changed.

Tweaked that and a few more things, then applied the result.

> I have kept the autovacuum message change as 0002 since Michael
> suggested unifying the format strings. If the consensus is to
> leave the existing autovacuum message alone, I'm happy to drop it.

This is useful on HEAD, so done that as 7905416eef9b.

Thanks,
--
Michael

Commits

  1. Use placeholders and not GUC names in error message (autovacuum)