Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit4817da5

Browse files
committed
worker_spi: Bump up max_worker_processes in TAP tests
mamba has detected a failure in the last test that should start abgworker while bypassing the role login check. The buildfarm did notprovide any information about its failure in the logs, but I suspectthat this is caused by an exhaustion of the max_worker_processes slotsset at 8 by default.In "normal" test runs, the number of bgworkers running at this stage ofthe test is already 7, so, if one of them spawns for example a parallelworker all the slots would be taken, preventing the last worker of thetest to start.Reviewed-by: Tom LaneDiscussion:https://postgr.es/m/ZSyebsiub88pyJJO@paquier.xyz
1 parent1f89b73 commit4817da5

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

‎src/test/modules/worker_spi/t/001_worker_spi.pl

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,11 +63,14 @@
6363
$node->safe_psql('mydb','CREATE EXTENSION worker_spi;');
6464

6565
# Now load the module as a shared library.
66+
# Update max_worker_processes to make room for enough bgworkers, including
67+
# parallel workers these may spawn.
6668
$node->append_conf(
6769
'postgresql.conf',q{
6870
shared_preload_libraries = 'worker_spi'
6971
worker_spi.database = 'mydb'
7072
worker_spi.total_workers = 3
73+
max_worker_processes = 32
7174
});
7275
$node->restart;
7376

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp