From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: worker_spi: Bump up max_worker_processes in TAP tests |
Date: | 2023-10-16 04:12:38 |
Message-ID: | E1qsEy5-000mk0-Uv@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
worker_spi: Bump up max_worker_processes in TAP tests
mamba has detected a failure in the last test that should start a
bgworker while bypassing the role login check. The buildfarm did not
provide any information about its failure in the logs, but I suspect
that this is caused by an exhaustion of the max_worker_processes slots
set at 8 by default.
In "normal" test runs, the number of bgworkers running at this stage of
the test is already 7, so, if one of them spawns for example a parallel
worker all the slots would be taken, preventing the last worker of the
test to start.
Reviewed-by: Tom Lane
Discussion: https://postgr.es/m/ZSyebsiub88pyJJO@paquier.xyz
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/4817da51f69ae7e965abf94aad01a4bab1404918
Modified Files
--------------
src/test/modules/worker_spi/t/001_worker_spi.pl | 3 +++
1 file changed, 3 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2023-10-16 04:39:17 | pgsql: Try to handle torn reads of pg_control in frontend. |
Previous Message | Thomas Munro | 2023-10-16 01:13:33 | Re: pgsql: Rename 005_login_trigger.pl to 006_login_trigger.pl |