From 980e8879f54a7a00ca6a5bae2fe9486c87ef3e8e Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Sun, 9 Apr 2023 08:27:36 +1200 Subject: Use higher wal_level for 004_io_direct.pl. The new direct I/O test deliberately uses a very small shared_buffers to force some disk transfers without making the data set large and slow, but ran into a problem with wal_level = minimal: log_newpage_range() pins many buffers, leading to a few intermittent "no unpinned buffers available" errors. We could presumably fix that by adjusting shared_buffers, but crake seems to be trying to tell us something interesting with these settings, so let's just avoid wal_level = minimal in this test for now. Reported-by: Andres Freund Discussion: https://postgr.es/m/20230408060408.n7xdwk3mxj5oykt6%40awork3.anarazel.de --- src/test/modules/test_misc/t/004_io_direct.pl | 1 + 1 file changed, 1 insertion(+) (limited to 'src') diff --git a/src/test/modules/test_misc/t/004_io_direct.pl b/src/test/modules/test_misc/t/004_io_direct.pl index f5bf0b11e4e..5a2dd0d288f 100644 --- a/src/test/modules/test_misc/t/004_io_direct.pl +++ b/src/test/modules/test_misc/t/004_io_direct.pl @@ -23,6 +23,7 @@ $node->append_conf( 'postgresql.conf', qq{ io_direct = 'data,wal,wal_init' shared_buffers = '256kB' # tiny to force I/O +wal_level = replica # minimal runs out of shared_buffers when set so tiny }); $node->start; -- cgit v1.2.3