Re: [PATCH] Warn when io_min_workers exceeds io_max_workers

From: Baji Shaik <baji(dot)pgdev(at)gmail(dot)com>
To: Tristan Partin <tristan(at)partin(dot)io>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Warn when io_min_workers exceeds io_max_workers
Date: 2026-06-23 01:27:13
Message-ID: CA+fm-RO3iQfdrvVA6C=0Oe126cbWNwePuwx2WL0XfPHB1BMj5g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 22, 2026 at 5:30 PM Tristan Partin <tristan(at)partin(dot)io> wrote:

> The code looks good. I wonder if we should add a test. I could not find
> a similar test for autovacuum for what it's worth.
>

Thanks for the review, Tristan.

I checked and confirmed there's no existing test covering the
check_av_worker_gucs() in autovacuum either. I'm happy to add a TAP
test if you think it's needed. Let me know and I will include it in v2.

Thanks,
Baji Shaik.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-06-23 01:29:35 Re: [PATCH] Warn when io_min_workers exceeds io_max_workers
Previous Message Richard Guo 2026-06-23 01:20:32 Re: Fix HAVING-to-WHERE pushdown with mismatched operator families