From: Michael Paquier <michael@paquier.xyz>
Date: Sun, 13 Oct 2024 02:20:30 +0000 (+0900)
Subject: Use MAX_PARALLEL_WORKER_LIMIT for max_parallel_maintenance_workers
X-Git-Tag: REL_18_BETA1~1731
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=c0b74323dc7b47644f074cf98597723ca55b2309;p=thirdparty%2Fpostgresql.git

Use MAX_PARALLEL_WORKER_LIMIT for max_parallel_maintenance_workers

max_parallel_maintenance_workers has been introduced in 9da0cc35284b,
and used a hardcoded limit of 1024 rather than this variable.

max_parallel_workers and max_parallel_workers_per_gather already used
MAX_PARALLEL_WORKER_LIMIT (1024) as their upper-bound since
6599c9ac3340.

Author: Matthias van de Meent
Reviewed-by: Zhang Mingli
Discussion: https://postgr.es/m/CAEze2WiCiJD+8Wig_wGPyn4vgdPjbnYXy2Rw+9KYi6izTMuP=w@mail.gmail.com
---

diff --git a/src/backend/utils/misc/guc_tables.c b/src/backend/utils/misc/guc_tables.c
index 686309db58b..2c4cc8cd41b 100644
--- a/src/backend/utils/misc/guc_tables.c
+++ b/src/backend/utils/misc/guc_tables.c
@@ -3463,7 +3463,7 @@ struct config_int ConfigureNamesInt[] =
 			NULL
 		},
 		&max_parallel_maintenance_workers,
-		2, 0, 1024,
+		2, 0, MAX_PARALLEL_WORKER_LIMIT,
 		NULL, NULL, NULL
 	},