Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 980e887

Browse files
committed
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 <andres@anarazel.de> Discussion: https://postgr.es/m/20230408060408.n7xdwk3mxj5oykt6%40awork3.anarazel.de
1 parent 064750a commit 980e887

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

src/test/modules/test_misc/t/004_io_direct.pl

+1
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@
2323
'postgresql.conf', qq{
2424
io_direct = 'data,wal,wal_init'
2525
shared_buffers = '256kB' # tiny to force I/O
26+
wal_level = replica # minimal runs out of shared_buffers when set so tiny
2627
});
2728
$node->start;
2829

0 commit comments

Comments
 (0)