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

Commit327d987

Browse files
committed
tests: Cope with io_method in TEMP_CONFIG in test_aio
If io_method is set in TEMP_CONFIG the test added in93bc3d7 fails,because it assumes the io_method specified at initdb is actually used.Fix that by appending the io_method again, after initdb (and thus afterTEMP_CONFIG has been added by Cluster.pm).Per buildfarm animal bumblebeeDiscussion:https://postgr.es/m/zh5u22wbpcyfw2ddl3lsvmsxf4yvsrvgxqwwmfjddc4c2khsgp@gfysyjsaelr5
1 parentbc22dc0 commit327d987

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

‎src/test/modules/test_aio/t/001_aio.pl‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,17 @@ sub create_node
9494
log_error_verbosity=default
9595
restart_after_crash=false
9696
temp_buffers=100
97+
));
98+
99+
# Even though we used -c io_method=... above, if TEMP_CONFIG sets
100+
# io_method, it'd override the setting persisted at initdb time. While
101+
# using (and later verifying) the setting from initdb provides some
102+
# verification of having used the io_method during initdb, it's probably
103+
# not worth the complication of only appending if the variable is set in
104+
# in TEMP_CONFIG.
105+
$node->append_conf(
106+
'postgresql.conf',qq(
107+
io_method=$io_method
97108
));
98109

99110
ok(1,"$io_method: initdb");

0 commit comments

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