From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jafri, Nazneen" <nazjafri(at)amazon(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL 18 Beta 1 io_max_concurrency |
Date: | 2025-05-14 19:25:58 |
Message-ID: | 9673.1747250758@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Jafri, Nazneen" <nazjafri(at)amazon(dot)com> writes:
> The default setting of parameter io_max_concurrency shows 64 whereas the documentation says -1, checking if this is the expected behavior.
I think it's behaving as designed: the bootstrap default is indeed -1, but
later in startup there is an an auto-tuning step that replaces that with
a number chosen as stated in the docs (which evidently comes out as 64
on your system).
There are other auto-tuned GUCs that behave similarly. We could leave the
user-exposed setting as "-1", but it was argued that that was unhelpful
compared to exposing the value chosen by auto-tuning.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mihail Nikalayeu | 2025-05-14 19:34:56 | Re: Small fixes needed by high-availability tools |
Previous Message | Andrey Borodin | 2025-05-14 18:13:58 | Re: Small fixes needed by high-availability tools |