summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndres Freund2025-04-02 10:56:29 +0000
committerAndres Freund2025-04-02 11:00:40 +0000
commit327d987df1e72a9b146f312df0a5ed34ef148720 (patch)
treedae878d06454465bb212e3bf6efa5fd60ee0c318
parentbc22dc0e0ddc2dcb6043a732415019cc6b6bf683 (diff)
tests: Cope with io_method in TEMP_CONFIG in test_aio
If io_method is set in TEMP_CONFIG the test added in 93bc3d75d8e 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 after TEMP_CONFIG has been added by Cluster.pm). Per buildfarm animal bumblebee Discussion: https://postgr.es/m/zh5u22wbpcyfw2ddl3lsvmsxf4yvsrvgxqwwmfjddc4c2khsgp@gfysyjsaelr5
-rw-r--r--src/test/modules/test_aio/t/001_aio.pl11
1 files changed, 11 insertions, 0 deletions
diff --git a/src/test/modules/test_aio/t/001_aio.pl b/src/test/modules/test_aio/t/001_aio.pl
index 93fe5b116df..e8d064ecd8d 100644
--- a/src/test/modules/test_aio/t/001_aio.pl
+++ b/src/test/modules/test_aio/t/001_aio.pl
@@ -96,6 +96,17 @@ restart_after_crash=false
temp_buffers=100
));
+ # Even though we used -c io_method=... above, if TEMP_CONFIG sets
+ # io_method, it'd override the setting persisted at initdb time. While
+ # using (and later verifying) the setting from initdb provides some
+ # verification of having used the io_method during initdb, it's probably
+ # not worth the complication of only appending if the variable is set in
+ # in TEMP_CONFIG.
+ $node->append_conf(
+ 'postgresql.conf', qq(
+io_method=$io_method
+));
+
ok(1, "$io_method: initdb");
return $node;