From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: worker_spi: Fix test failure with BGWORKER_BYPASS_ROLELOGINCHECK |
Date: | 2023-10-16 04:48:44 |
Message-ID: | E1qsFX1-000n4b-OE@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
worker_spi: Fix test failure with BGWORKER_BYPASS_ROLELOGINCHECK
This is a consequence of 4817da51f69a that has bumped up
max_worker_processes, where now the last worker started by the test
would be able to start by itself a parallel worker because there are
more slots available. This did not show up before as the number of
bgworkers reached exactly 8, as known as the previous limit, at the end
of the test.
Per report from buildfarm member crake, reproducible with
debug_parallel_query = regress in the same fashion as fd4d93d269c0.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/4922173010f102a7d56af7c97bd303b95b3f6eff
Modified Files
--------------
src/test/modules/worker_spi/worker_spi.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2023-10-16 07:40:26 | pgsql: List 006_login_trigger.pl test for meson |
Previous Message | Thomas Munro | 2023-10-16 04:40:08 | pgsql: Try to handle torn reads of pg_control in frontend. |