From f50753f303e8969610f28f3a64f81be4b5f5594b Mon Sep 17 00:00:00 2001 From: Matthijs Mekking Date: Wed, 12 Mar 2025 16:48:54 +0100 Subject: [PATCH] Update max-clients-per-query documentation The new intended behavior is that 'max-clients-per-query' value is raised to equal 'clients-per-query' if it is lower. --- doc/arm/reference.rst | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index c4245cf869..612fda7ad4 100644 --- a/doc/arm/reference.rst +++ b/doc/arm/reference.rst @@ -3660,9 +3660,13 @@ system. after 20 minutes if it has remained unchanged. If :any:`max-clients-per-query` is set to zero, there is no upper bound, other - than that imposed by :any:`recursive-clients`. If :any:`clients-per-query` is - set to zero, :any:`max-clients-per-query` no longer applies and there is no - upper bound, other than that imposed by :any:`recursive-clients`. + than that imposed by :any:`recursive-clients`. If the option is set to a + lower value than :any:`clients-per-query`, the value is adjusted to + :any:`clients-per-query`. + + If :any:`clients-per-query` is set to zero, :any:`max-clients-per-query` no + longer applies and there is no upper bound, other than that imposed by + :any:`recursive-clients`. .. namedconf:statement:: max-validations-per-fetch :tags: server