database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

tests: Cope with io_method in TEMP_CONFIG in test_aio

Browse Source 
If io_method is set in TEMP_CONFIG the test added in 93bc3d75d8 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
This commit is contained in:
Andres Freund
2025-04-02 06:56:29 -04:00
parent bc22dc0e0d
commit 327d987df1
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
src/test/modules/test_aio/t/001_aio.pl
View File

@ -94,6 +94,17 @@ log_statement=all
log_error_verbosity=default
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");